Re: nslcd starts failing logins after about an hour.

[Arthur de Jong <arthur [at] arthurdejong.org>]

On Mon, 2011-05-16 at 18:48 -0600, Jason J. W. Williams wrote:
> > If you have a network connection through a firewall it could be that the
> > connection is broken without the LDAP library noticing (or that the
> > server just closed the connection). This could also account for the
> > extra delay (nslcd doesn't detect broken connection that quickly).
> >
> > To work around this you could use the idle_timelimit option in
> > nslcd.conf to close the connection once the timeout has expired. This
> > should ensure quicker reconnection.
> 
> Even with idle_timeout the latency of the first login after awhile is
> still the same.

Can you provide debugging output from nslcd when this reconnection
happens? It could be that some error is logged and something can be
improved. Is it much slower than the initial connect to the LDAP server?

-- 
-- arthur - arthur@arthurdejong.org - http://arthurdejong.org --

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users