Hi,
On Sun, 9 Mar 2014, michael@stroeder.com wrote:
hyc@symas.com wrote:
I'd consider instead, resurrecting the LDAP_DEBUG_INDEX debug flag, or putting these in LDAP_DEBUG_FILTER. TRACE is already too verbose.
I'm fine with any solution which avoids that these messages are sent to the log in case of "loglevel stats stats2".
I would also welcome a separate loglevel for these daemon messages:
Mar 9 11:00:24 ldap1 slapd[19539]: daemon: read activity on 9 Mar 9 11:00:24 ldap1 slapd[19539]: daemon: select: listen=6 active_threads=0 tvp=zero Mar 9 11:00:24 ldap1 slapd[19539]: daemon: select: listen=7 active_threads=0 tvp=zero Mar 9 11:00:24 ldap1 slapd[19539]: daemon: activity on 1 descriptor Mar 9 11:00:24 ldap1 slapd[19539]: daemon: waked Mar 9 11:00:24 ldap1 slapd[19539]: daemon: select: listen=6 active_threads=0 tvp=zero Mar 9 11:00:24 ldap1 slapd[19539]: daemon: select: listen=7 active_threads=0 tvp=zero
They currently seem to be triggered by loglevel conns.
So what about adding loglevel daemon or even conns2 for these.
Greetings Christian