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.
I recently tried to upgrade an older server where I only need winbindd. I run it under daemontools and that has stopped working. The man pages and the output of 'winbindd --help' both are no longer correct. I have struggled with this and eventually found a way to get it to start in the foreground. To achieve what used to be done by 'winbindd -i' now requires 'winbindd -F --no-process-group --debug-stdout'. Just plain 'winbindd -F' doesn't do anything and just comes back to the prompt. To get -F to accomplish anything you need both --no-process-group and --debug-stdout. This workaround works with both samba 4.16 and 4.19.