Hi, slapd can send its logs and messages to syslog, which is nice and good in common Unix/Linux environments, but I didn't see any way to have the logs sent to stdout/stderr instead of syslog. When run in a docker/kubernetes container, which is a typical use nowadays, it should be run as a single process, and not require a separate syslog process just to write some logs to a file. There are dirty workarounds, but if run cleanly, it should be a standalone process. Therefore, it would be nice if slap had a container mode, where - it doesn't fork (currently available only through debugging mode) - sends logging to stdout/stderr instead of syslog regards
This would be appreciated by users of other service supervisors too, such as systemd, runit, s6, etc. Running in foreground with logging to stderr (not stdout, please) is becoming a more and more typical setup in general, not only for debugging.
(In reply to Ryan Tandy from comment #1) > This would be appreciated by users of other service supervisors too, such as > systemd, runit, s6, etc. Running in foreground with logging to stderr (not > stdout, please) is becoming a more and more typical setup in general, not > only for debugging. That's already what happens when you run with -d. I see nothing to change here. Closing this ITS.