From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: Cygwin Mailing List <cygwin@cygwin.com>
Subject: timeout in LDAP access
Date: Mon, 16 Jun 2014 20:39:00 -0000 [thread overview]
Message-ID: <F312783D-AD66-4614-922B-E44403C7E372@Denis-Excoffier.org> (raw)
Hello,
I’ve exercised ‘getent' a little bit those days (with 'db_enum: all’ in /etc/nsswitch.conf), and it seems to me
that the timeout ‘tv' (3 seconds, in ldap.cc) is probably too small for servers not so quickly responsive
or with many (500000, fake or real) users around (see the call to ldap_get_next_page_s()). 300 seconds should be
enough i suppose.
Also it is a pity that LDAP_TIMEOUT is not announced to the user (except under strace: 0x55). I don’t know the
general policy for timeouts, but i consider that the user would like to be informed when the passwd/group list was
truncated.
Another (unrelated and less important) problem is that 'getent' happily produces lines with some extra ‘:’, in
particular when the gecos field itself contains ‘:’.
Regards,
Denis Excoffier.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2014-06-16 20:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 20:39 Denis Excoffier [this message]
2014-06-17 10:00 ` Corinna Vinschen
2014-06-17 10:30 ` gecos from AD? (was Re: timeout in LDAP access) Corinna Vinschen
2014-06-17 12:51 ` Corinna Vinschen
2014-06-17 23:07 ` Denis Excoffier
2014-06-18 2:18 ` AW: " Christoph H. Hochstaetter
2014-06-17 22:59 ` Denis Excoffier
2014-06-18 8:38 ` Corinna Vinschen
2014-06-17 22:41 ` timeout in LDAP access Denis Excoffier
2014-06-18 8:33 ` Corinna Vinschen
2014-06-18 18:01 ` Corinna Vinschen
2014-06-19 17:53 ` Denis Excoffier
2014-06-23 9:10 ` Corinna Vinschen
2014-06-23 20:38 ` Denis Excoffier
2014-06-24 15:59 ` Corinna Vinschen
2014-06-25 10:15 ` Corinna Vinschen
2014-06-25 20:44 ` Denis Excoffier
2014-06-25 21:14 ` Corinna Vinschen
2014-07-03 20:57 ` Denis Excoffier
2014-07-07 11:07 ` Corinna Vinschen
2014-07-08 19:34 ` Denis Excoffier
2014-07-09 10:13 ` Corinna Vinschen
2014-07-12 13:39 ` Denis Excoffier
2014-07-14 9:51 ` Corinna Vinschen
2014-07-14 13:48 ` Corinna Vinschen
2014-07-15 16:29 ` Denis Excoffier
2014-07-15 18:20 ` Andrey Repin
2014-07-16 13:52 ` Corinna Vinschen
2014-07-17 6:33 ` Denis Excoffier
2014-07-18 19:18 ` Corinna Vinschen
2014-07-28 9:21 ` Corinna Vinschen
2014-07-28 18:51 ` Denis Excoffier
2014-07-29 9:07 ` Please test AD integration changes, documentation attached (was Re: timeout in LDAP access) Corinna Vinschen
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=F312783D-AD66-4614-922B-E44403C7E372@Denis-Excoffier.org \
--to=cygwin@denis-excoffier.org \
--cc=cygwin@cygwin.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).