Followup-For: Bug #759544 Hi,
> Could you also test > http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=a726d291b0f6794abec0a0192cf2b2a742648e4a > to see if that helps. It should give a little more information on why > start-up failed. I have built a local package with that patch and just observed this issue. Apr 13 12:40:32 pgdb2 ifup[588]: Sending network state change signal to nslcd...done. Apr 13 12:40:32 pgdb2 nslcd[686]: Starting LDAP connection daemon: nslcdnslcd: wait_for_response(): read_response() returned 0 (expected 4) Apr 13 12:40:32 pgdb2 nslcd[686]: nslcd: unable to daemonize: No data available Apr 13 12:40:32 pgdb2 nslcd[686]: failed! Does that help? I still think it is caused by a race between the ifupdown trigger and nslcd startup. Best Regards, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
