Bug 15570 - winbindd (samba-4.17-stable and newer versions) fails to enter on interactive and foreground mode
Summary: winbindd (samba-4.17-stable and newer versions) fails to enter on interactive...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.17.12
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-06 13:45 UTC by aristeu.jr
Modified: 2024-02-06 13:57 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description aristeu.jr 2024-02-06 13:45:40 UTC 
Since what appears to be this commit on the code [1], winbindd can no longer start on -i (interactive mode) nor -F (foreground) mode.

[1] https://gitlab.com/samba-team/samba/-/commit/3467214cf967641f4e4001a9dfea870f933fc2a3

Reproducing the problem:
It happens in bare metal also, but with docker is how to reproduce it easily:

# docker run --rm -it debian:bookworm bash

And inside docker:

root@20a43b65b638:/# apt-get update && apt-get install -y winbind

root@20a43b65b638:/# winbindd -i

ERROR: Can't log to stdout (-S) unless daemon is in foreground (-F) or interactive (-i)

Usage: winbindd [-?nDiFV] [-?|--help] [--usage] [-n|--no-caching] [-d|--debuglevel=DEBUGLEVEL] [--debug-stdout] [-s|--configfile=CONFIGFILE]
        [--option=name=value] [-l|--log-basename=LOGFILEBASE] [--leak-report] [--leak-report-full] [-D|--daemon] [-i|--interactive]
        [-F|--foreground] [--no-process-group] [-V|--version]


root@20a43b65b638:/# winbindd -V
Version 4.17.12-Debian


What is expected to happen:
Daemon starts on interactive or foreground mode and logs activities to stdout.