Package: libnss-ldapd Version: 0.6.2 Every 5 minutes on my clients, nslcd report that an LDAP search failed and that it had to reconnect. This is not really very interesting as it is perfectly normal for the LDAP server to disconnect unused connections, and for nslcd to reconnect when this happen.
I am actually using the svn version backported to Etch here, but believe it will behave the same way on Lenny. Here is an example: May 31 12:45:01 test.local nslcd[11354]: [304a67] ldap_result() failed: Can't contact LDAP server May 31 12:45:01 test.local nslcd[11354]: [304a67] connected to LDAP server ldap://adserver.local/ May 31 12:50:01 test.local nslcd[11354]: [b180d8] ldap_result() failed: Can't contact LDAP server May 31 12:50:01 test.local nslcd[11354]: [b180d8] connected to LDAP server ldap://adserver.local/ May 31 12:55:02 test.local nslcd[11354]: [6b69ed] ldap_result() failed: Can't contact LDAP server May 31 12:55:02 test.local nslcd[11354]: [6b69ed] connected to LDAP server ldap://adserver.local/ Can this syslogging be changed to only report when the reconnect fail, and not when it succeed like it does here? It fill up the syslog and make it harder to see real issues in the log. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
