Package:  libnss-ldapd
Version:  0.2
Severity: wishlist

One of the nice things about NIS, is the client side failover that is
implemented in ypbind.  This make it very robust against failures.
Here at the university, we have a lot of NIS servers, and for networks
behind a problematic link, we tend to place one NIS server on the
local network.  All clients are given four NIS servers to use, and the
fastest one of these will be automatically used.  We are currently
considering switching to LDAP instead of NIS.

It would be great if libnss-ldapd had a similar feature.  I want to be
able to list serveral LDAP servers in the config file, and for the
nslcd program to test each of these at a regular interval (ypbind
checks every 15 minutes) and switch to the fastest one.  If the
currently used LDAP server fail to reply, it should switch to the
fastest one of the remaining servers.

Please consider implementing such feature.

Happy hacking,

nss-ldapd allows you to specify more than one URI in the config file
(configuration with Debconf also lets you specify multiple URIs).

nss-ldapd users a fail-over mechanism to the second configured LDAP
server if the connection to the first server failed. nss-ldapd then
sticks with the working LDAP server until that one fails.

nss-ldapd currently does not do any checking for which server is the
fastest and uses a simple round-robbin mechanism. Smarter switching
between LDAP servers may be implemented in a later release, but the
development focus for now is on getting the system as stable and
maintainable as possible.