--- Comment #23 from Shawn McKinney <smckinney(a)symas.com> ---
1. When logfile-only on and logfile is not specified:
a. no messages route to syslog or stderr (documented in slapd-config.5, not
b. this message *always* goes to syslog: "Mar 22 16:52:52 p01 slapd:
/opt/symas/etc/openldap/slapd.conf: line 10 (logfile-only on)"
i. Which is good for troubleshooting
c. Turns off *all* logging
2. When logfile-only on and logfile is specified:
a. debug messages -d go to logfile. (documented in slapd-config.5 "Specifying
a logfile copies messages to both stderr and the logfile.")
b. both -d and loglevel control logfile granuarlity, and are additive.
i. e.g. -d packets and loglevel stats both routed to the specified logfile.
3. When logfile-only is not on and a logfile is specified:
a. debug messages go to logfile and stderr, and are controlled by -d param
b. loglevel goes to syslog (only) and are controlled by -s or loglevel.
c. a & b are documented in slapd-config.5, not admin guide.
d. Settings -d and loglevel have differences.
i. e.g. loglevel sync includes stats where -d sync doesn't. (undocumented)
4. loglevel settings in slapd config take precendence over command line -s,
i.e. not additive (undocumented)
5. loglevel or -s 'packets BER parse' don't go to the logfile. Use '-d
instead (documentation not clear)
You are receiving this mail because:
You are on the CC list for the issue.