On Mon, Jan 08, 2007 at 10:03:09PM -0800, dean gaudet wrote: > when the ldap server closes the connection during a response, libnss-ldap > doesn't really notice at all... it returns an error code to the caller but > doesn't pay attention to the error code itself. then nscd (or whatever > other caller is involved) tries to re-open a new connection and > libnss-ldap decides that someone has stolen its old socket and proceeds to > leak the socket.
Seems reasonable; I built a patched libnss-ldap and am running it on one of our affected machines. We'll see in a day or two. thanks! john -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
