--On Tuesday, July 31, 2007 4:35 AM +0000 ando@sys-net.it wrote:
quanah@zimbra.com wrote:
Full_Name: Quanah Gibson-Mount Version: 2.3.37 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (66.92.25.194)
When using cn=config with a slapd.conf driven slapd, the value for olcLogLevel is not correct:
ldapsearch -LLL -x -h build -b "cn=config" -s base -D "cn=config" -W olcLogLevel Enter LDAP Password: dn: cn=config olcLogLevel: None
However:
grep loglevel conf/slapd.conf loglevel 32768
And the logging that is happening is actually for level 32768. Modifying the loglevel works, and once that is done, the right loglevel is shown. However, this makes it impossible to know what loglevel is set via a remote query unless it has been changed.
From slapd.conf(5), loglevel:
32768 (0x8000 none) only messages that get logged whatever log level is setSeems to be correct.
Yet if I modify it to be "256", then olcLogLevel is "256". If I modify it to be "32768", then it is "32768". So if the loglevel setting in slapd.conf is "32768", then that is what it should match. In any case, "None" has the unfortunate ring of sounding like an unset value.
--Quanah
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
-
quanah＠zimbra.com