From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: timeout in LDAP access
Date: Tue, 24 Jun 2014 15:59:00 -0000 [thread overview]
Message-ID: <20140624155851.GJ1803@calimero.vinschen.de> (raw)
In-Reply-To: <C2FB35D9-AE47-4461-8A94-20605D5EB996@Denis-Excoffier.org>
[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]
On Jun 23 22:38, Denis Excoffier wrote:
> On 2014-06-23 11:09, Corinna Vinschen wrote:
> > On Jun 19 19:53, Denis Excoffier wrote:
> >
> > Do you really *want* to enumerate 500K users when accessing the DCs
> > remote over a slow DSL line? Isn't this a situation in which you'd
> > rather like to avoid enumerating accounts or restrict it to an
> > essential subset? That's what db_enum would be good for.
> IMHO the line is not especially slow. Instead, the
> server (and occasionally the client) is clobbered sometimes. For example it
> seems more difficult (ie timeout occurs more frequently) for a server
> to output the last sid’s in a domain than to output a full PageSize of
> results.
>
> Personally i don’t *want* to use /etc/nsswitch.conf at all. What bothers me
> is that the user does not get any indication of a timeout (and several successive
> and unrelated timeouts may be met in a single invocation of getent). Therefore
> even if all servers are up, the user has no means to know that the list is exhaustive.
> If the timeout occurs for the last chunk this is not so important, but if
> the timeout occurs in the middle it may be. That is the difference between
> a large timeout and a timeout, say, too accurate.
> [...]
> >> 1) for most of the 100-sid chunks, the high timeout is not used, therefore
> >> the global penalty in delay is not so high. And perhaps a 120s timeout is high
> >> enough so that when it is met, we could abandon not only the current domain,
> >> but also the whole search?
> >
> > Would that be really a bright idea? Assuming your ADs (and their DCs)
> > are in different remote locations, One of those connections being down
> > would disable enumerating other domains.
> It would be a means to have getent 'depend' on a unique timeout.
> >
> >> 2) if value of timeout is not high enough (i have no figures…), timeout may
> >> occur when the PC is in fact occupied with other tasks (eg antivirus scanning
> >> or something else), unrelated to network delays or server latencies.
> >
Stay tuned. I'm rewriting the LDAP access code to perform all critical
LDAP calls in interruptible threads. The Windows LDAP calls don't
provide any kind of synchronization, only timeouts. I hoped to get away
with short timeouts but it seems I hoped in vain.
So the next iteration of this code will not use any timeout other than
the default LDAP network timeout of 2 minutes, but the calls will be
interruptible by signals.
I hope that fixes this the right way :}
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-24 15:59 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
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 [this message]
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=20140624155851.GJ1803@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).