On Mon, Aug 21, 2006 at 11:23:39PM -0400, Jamin W. Collins wrote: > > It might also be worth noting that this same configuration was not a > problem under sarge. The problem did not occur until I upgraded my > system from sarge to etch on Sunday. Then the boot process broke due to > the libnss-ldap changes (ldap then compat no longer worked in > /etc/nsswitch.conf, but that's a different bug report). Once > /etc/nsswitch.conf was changed to files then ldap the boot process at > least continued. Then I found this problem. > > It seems that some change with libnss-ldap between sarge and etch is > wreaking havoc on configurations that have thus far been working fine. > I know of breakage within at least three different locations related to > the changes (boot, dbus/hal, and now this).
My opinion is that there is a SIGPIPE which is not catched at one of these levels: libnss-ldap, libc, or perl. This could be related to the bug 190072 (libnss-ldap: Processes may receive SIGPIPE from LDAP session timeouts), but this bug was present in Sarge. Also, it could be interresting to test with the previous versions of libnss-ldap to see when the problem appeared, or with the patch attached to 190072. I have no LDAP box, so I can't test. I would appreciate if you could. You can test with the single perl command sent in the previous messages to this bug. Kind Regards, -- Nekral -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]