Control: tags -1 + pending Control: found -1 nss-ldapd/0.6.2 On Tue, 2013-10-15, Lisandro Damián Nicanor Pérez Meyer wrote: > /etc/init.d/nslcd should add $network to Required-Start (and possibly > to Required-Stop) to be able to contact the LDAP server. > > What I'm seeing in my systems is that sometimes nslcd gets started > before an IP is provided by a DHCP server (yes, I don't have static > IPs in this place). > > Then it can't reach the LDAP server.
Thanks for reporting this. The dependency on $network was dropped in version 0.6.2 while fixing #478807. At the time, it was assumed that $remote_fs implicitly depends on $network so the explicit dependency was no longer needed. I will re-add the Should-Start and Should-Stop dependencies in the next upload. One minor note though: the description of what $network implies differs a bit from Debian (the LSBInitScripts wiki page says "low level networking (ethernet card; may imply PCMCIA running)") and the LSB (LSB 3.1 says "basic networking support is available. Example: a server program could listen on a socket."). Neither of these guarantee that a route to the LDAP server is available. If you're using NetworkManager I don't think you can give any guarantees as to when, during the boot sequence, the interface becomes available. The 0.9.1-1 version of nss-pam-ldapd includes an if-up script and change in nslcd to re-check the reachability of the LDAP server quickly after a network connection is established which should fix more problem-cases. Thanks, -- -- arthur - [email protected] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
