Package: nslcd
Version: 0.7.13
When one or more uri statements are added to /etc/nslcd.conf with the
names of available LDAP servers, nslcd works just fine. However, if
only "uri DNS" is used, nslcd is not reliable in finding the available
LDAP servers, despite the necessary DNS SRV RRs being available.
Sample error:
nslcd[1196]: [8b4567] failed to bind to LDAP server
ldap://ldap.example.com/: Can't contact LDAP server: No such file or
directory
The problem usually occurs during bootup; typically it works perfectly
when restarted manually afterwards. Sometimes the problem is that
nslcd attempts to locate an LDAP server in the local domain, instead
of in the domain indicated by the "base" statement in /etc/nslcd.conf.
Still, the combination of libnss-ldapd and nslcd (with kstart) is a
definite step forwards for my site. Once the DNS lookup problems have
been resolved, I would like to suggest that this become the default
for nslcd, just as it is with libnss-ldap, i.e. no uri value(s), or an
empty one, means that nslcd should look for LDAP servers using DNS.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
