[Bug nscd/2132] Use nscd to support disconnected LDAP operation

[howard at cohtech dot com]

------- Additional Comments From howard at cohtech dot com  2009-10-27 13:58 -------
I suspect that the real cause of the problems described below are in the 
nss_ldap code.

I have looked into the nss_ldap code and it responds with NSS_STATUS_UNAVAIL, 
errno = EPERM for the following cases.

LDAP_SERVER_DOWN, LDAP_TIMEOUT, LDAP_UNAVAILABLE, LDAP_BUSY, 
LDAP_CONNECT_ERROR, LDAP_LOCAL_ERROR, LDAP_INVALID_CREDENTIALS.

The last 2 are, I suspect, correct but the first 5 are really candidates 
for 'server has gone away'. I suspect, but can't quite decide whether I am 
right, that the code should respond with NSS_STATUS_TRYAGAIN, errno = EAGAIN 
for the cache to continue to be populated with the entry.

If anybody who understands the nsswitch internals can confirm which is the 
correct response I will patch the nss_ldap library (I have half a patch 
already) and try this out.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2132

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.