[Arthur de Jong] > Thanks for reporting this. Just to be clear, you are seeing this > with libnss-ldapd 0.6.7.1 and 0.7.1?
I'm seing this with version 0.7.1 backported to Lenny. I suspect it also was in 0.6.7.1, but did not really investigate that, as I upgraded libnss-ldapd to see if it would give me quicker login and then started looking into the problem when it didn't. > Can you also reproduce this with just 'getent group' (or id -a user)? Nope. Those do not cause nscd to crash. > Does it make a difference if nscd is running or not? Both those commands behave the same with nscd running and not. > Does cleaning the nscd cache make a difference (nscd -i passwd; nscd > -i group)? The crash still happened after I ran these two commands before starting nscd using valgrind. > If this is a problem with the communication between nscd and the NSS > module, recompiling the NSS module with -DDEBUG_PROT (and maybe even > -DDEBUG_PROT_DUMP) could give a lot more details. Warning: this > causes every command that does NSS lookups (through LDAP) to output > a lot of debugging information. I am reluctant to enable that much debugging with 8000 file groups in LDAP. :/ Anyway, I gave it a try and was flodded with messages. No idea which one are relevant, and ran out of time to debug any further. Not sure if it would crash either, as I had to kill the process before I run to install a version without so much noise. > Does changing +...@netgroup to just + make a difference (haven't set this > up in my test environment)? Yes. Removing the +...@netgroup entries made nscd crash later (ie my ssh login completed before the crash, as opposed to at the same time as the crash with the +...@netgroup entries in place. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
