On 09/11/11 09:08, Arthur de Jong wrote:
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,
Hi.
I use nscd for caching.
I also noticed that if I am off-line, I am not able to fully login to my
window manager (xfce4, kde4). The login part seems to finish
successfully and I receive a message that I am using cached credentials,
however the screen stays black after that. nslcd logs problems to find
the LDAP again. If I stop the nslcd service, before the login, the
windows manager comes up no problem.
Something does not seems to work correctly with nslcd...
Thank you for looking into this.
Jiri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
