public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howard at cohtech dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/2132] Use nscd to support disconnected LDAP operation
Date: Tue, 27 Oct 2009 13:59:00 -0000	[thread overview]
Message-ID: <20091027135846.10615.qmail@sourceware.org> (raw)
In-Reply-To: <20060109232507.2132.redhat@flyn.org>


------- 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.


  parent reply	other threads:[~2009-10-27 13:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 23:25 [Bug nscd/2132] New: " redhat at flyn dot org
2006-01-09 23:41 ` [Bug nscd/2132] " drepper at redhat dot com
2006-01-10  1:39 ` redhat at flyn dot org
2006-01-10  3:02 ` drepper at redhat dot com
2006-02-12 15:24 ` redhat at flyn dot org
2007-02-18  4:49 ` drepper at redhat dot com
2007-04-05 14:10 ` costinel at gmail dot com
2007-04-05 14:25 ` costinel at gmail dot com
2009-10-22  3:33 ` brian at interlinx dot bc dot ca
2009-10-24 14:22 ` brian at interlinx dot bc dot ca
2009-10-24 15:07 ` brian at interlinx dot bc dot ca
2009-10-25 22:51 ` drepper at redhat dot com
2009-10-26 20:09 ` dqarras at yahoo dot com
2009-10-27 13:59 ` howard at cohtech dot com [this message]
2009-11-01 14:49 ` arthur at arthurdejong dot org
2009-11-01 17:48 ` dqarras at yahoo dot com
     [not found] <bug-2132-131@http.sourceware.org/bugzilla/>
2011-09-17 14:12 ` dqarras at yahoo dot com
2012-05-03 19:14 ` dqarras at yahoo dot com
2013-01-21  3:29 ` carlos at systemhalted dot org
2014-02-16 17:43 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-05-28 19:46 ` schwab at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091027135846.10615.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).