Re: [nssldap] Connection persistence

[Howard Chu <hyc [at] highlandsun.com>]

Arthur de Jong wrote:
> On Thu, 2010-11-04 at 16:59 +0000, James Davis wrote:
> > I'm starting to get my head around the documentation and the behavior.
> >
> > I'd expected the failover to be system-wide operation that persisted
> > between different processes whereas in fact the failover occurs once per
> > process. Running ls a second time requires the failover to happen again.
> > By using nscd, a single daemon process deals with libnss-ldap holding
> > that persistent connection open as desired.
> >
> > I think I understand now :) I'll see how this works out for me and if
> > necessary use something like pen to load balance.
>
> If you're looking for a solution that can keep a little more state you
> may be interested in nss-pam-ldapd (shameless plug here). It started out
> based on nss_ldap but has a local daemon that connects to the LDAP
> server. You can more debug fail-overs (and other things) more easily
> because ik can run in debug mode.
>
> You can even use it with the nssov overlay in slapd to provide the local
> daemon part and increase the reliability even further (using replication
> or caching).
>
> Hope this helps

More shameless plugging. I think nss-pam-ldapd is the only smart solution 
going forward. (Of course I recommend using it with nssov. Interested parties 
can download a turnkey package from www.symas.com.)

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/