[Arthur de Jong] > I was refering to the version of libldap2-dev, sorry I should've been > clearer.
Ah. It was built against libldap2-dev version 2.1.30-13.3. > You could also try to just run configure from the source tarball and > run the resulting nslcd. Passing --enable-debug to configure may > also include some more information. OK. > Could you test that for me and report the output on stderr (or part > of it) and possibly valgrind output? It got rid of the uninitialised values issues reported by valgrind, which is great. With this new version, I've been unable to reproduce the crash, but as I said before, it is hard to trigger, so I am not sure it is gone. I tried using this test script several times, without any luck getting it to crash. #!/bin/sh set -x # Remove sensitive information valgrind nslcd -d 2>&1 | sed 's/CN=.*,DC=LOCAL/CN=...,DC=LOCAL/' & pid=$! sleep 2 time id slxtest1 sleep 2 time id slxtest2 sleep 2 time id slxtest3 sleep 2 kill $pid wait I remove the LDAP CN info to avoid exposing the real group names to the public. A log of one of the test runs are available from <URL: http://people.skolelinux.no/pere/nslcd-log.txt >. Note the 'nslcd: error writing to client' messages. Can these be a problem? It seem to me that the server continue to work after the client return. That can't be how it is supposed to work? Please let me know if I removed too much from the log. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
