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.
-mike
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@olp.net:
You could direct your syslog daemon to ignore those messages. Look for lines which include:
*.debug local4.debug local4.*
I don't use syslogd, I run socklog-unix and socklog-klog services which are running under svlogd and listen directly to the OS's standard logging socket. I don't want to wholesale discount local4 messages because they might come from something else than slapd running in the foreground.
-mike
Dan White wrote:
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:
Or you could just set loglevel to 0 so no messages are produced.
*.debug local4.debug local4.*
Quoting Dan White dwhite@olp.net:
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.
-mike
Am Fri, 16 May 2014 20:53:39 +0300 schrieb Mike Jackson mj@netauth.com:
Quoting Dan White dwhite@olp.net:
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.
If you want to disable logging, just set loglevel 0 in slapd.conf or olcLogLevel 0 in cn=config
-Dieter
Am Fri, 16 May 2014 20:53:39 +0300 schrieb Mike Jackson mj@netauth.com:
Quoting Dan White dwhite@olp.net:
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.
the messages you recieve on stdout are debug messages not log messages. [...]
-Dieter
openldap-technical@openldap.org
-
Dan White -
Dieter Klünter -
Howard Chu -
Mike Jackson