From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: timeout in LDAP access
Date: Wed, 18 Jun 2014 18:01:00 -0000 [thread overview]
Message-ID: <20140618180102.GA27055@calimero.vinschen.de> (raw)
In-Reply-To: <20140618083304.GV23700@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
On Jun 18 10:33, Corinna Vinschen wrote:
> On Jun 18 00:41, Denis Excoffier wrote:
> > On 2014-06-17 12:00, Corinna Vinschen wrote:
> > > I'm wondering if the timeout, at least for enumerating accounts, should
> > > go away entirely. In case of a connection problem this could result in
> > > a hang for about 2 minutes by default I think (LDAP_OPT_PING_LIMIT).
> > I think i like this (it it works). But in this case, it will not resume
> > to the next domain, and the whole operation (eg getent) is interrupted?
>
> I don't quite understand the question. All LDAP operations have a
> default timeout of 2 minutes if LDAP_OPT_TIMEOUT is not set. The
> operations we're doing here are pretty simple ones, the bunch of 100
> SIDs per getpwent LDAP call is a really small dataset (about 4K bytes)
> of indexed data, which should be readily available. And there's a
> certain (not Cygwin-specific) expectation that a simple LDAP operation
> is fast.
>
> Assuming the server takes more than just 3 seconds to reply to
> a single request for some reason, let's say 30 seconds. The call will
> result in a laming output of getent, of course, but it would have no
> other consequences. If the server needs actually more than two minutes
> to reply, and doesn't return a ping either, the timeout is a very likely
> indication that we have network problems, or the server is down.
> In that case, the normal code path applies. The connection with the
> server will be closed and we try the next domain.
>
> The idea I was proposing was just to drop all attempts to seconds guess
> how fast a DC replies. We're going to use LDAP with default settings
> and that's it. Default settings means, every operation times out after
> the default timeout period of 120 seconds, which should really be
> sufficient.
I'm not quite sure I understand the effect of all the timeout values in
LDAP entirely correctly and the API documentation leaves quite a bit to
be desired.
For the time being I raised the timeout to 30 seconds, and colons in
the gecos field are converted to semicolons. I uploaded a new developer
snapshot to http://cygwin.com/snapshots/ Please give it a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-18 18:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 20:39 Denis Excoffier
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 [this message]
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=20140618180102.GA27055@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).