On Tue, 2011-11-08 at 13:06 +1100, Jiri Kanicky wrote: > When I unplug notebook from my network, nslcd is not able to contact LDAP > server and some task like "clicking on logout" takes long time and the > following errors are reported. > I believe that the nslcd is waiting for responce, and than the task can > proceed, but it should not work like that. In Windows, I also do not wait for > tasks when I work offline.
If you want to support off-line operation you either have to have a local replica of the LDAP server of perform some caching with nscd (or something else). Currently nss-pam-ldapd does not implement caching. If the connection to your LDAP server is normally reliable, you could tune the timing settings to something like this: bind_timelimit 3 timelimit 3 reconnect_sleeptime 1 reconnect_retrytime 3 This ensures that unavailability of the LDAP server is recorded quickly. > Nov 8 12:46:24 knightrider nslcd[2146]: [e3dfe6] <passwd=10001> no available > LDAP server found: Server is unavailable It is a bit strange that this query is retried so often because I would expect nscd to have cached the result. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
