Hi, Is there a way to prevent slapd from using syslog when running in the foreground? I run slapd permanently under the runit process supervision package with -d 256, and it already captures stderr to it's own logging system. However, I also get the same log messages cluttering up my syslog with local4.debug lines. Running in the foreground is pretty much a requirement for using process supervision and almost every service related software supports it for this reason. The background logging, despite running in the foreground, is undesired behavior.

On 05/16/14 12:12 +0300, Mike Jackson wrote: > Hi, > > Is there a way to prevent slapd from using syslog when running in the > foreground? I run slapd permanently under the runit process > supervision package with -d 256, and it already captures stderr to > it's own logging system. However, I also get the same log messages > cluttering up my syslog with local4.debug lines. Running in the > foreground is pretty much a requirement for using process supervision > and almost every service related software supports it for this reason. > The background logging, despite running in the foreground, is > undesired behavior. You could direct your syslog daemon to ignore those messages. Look for lines which include:

*.debug local4.debug local4.*

Quoting Dan White <dwhite(a)olp.net&gt;: > You could direct your syslog daemon to ignore those messages. > Look for lines which include: > > *.debug > local4.debug > local4.* That, of course, is not my goal. I want my stderr logs, outside of my syslog. No, I don't understand why when one puts a daemon into the foreground that it logs behind your back anyway, but it's not a huge deal. I'll patch it to suit my needs if nobody else agrees with me that this is undesirable behaviour. Of course, my patch would be submitted for consideration into the project.