From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: cygwin@cygwin.com
Subject: Re: timeout in LDAP access
Date: Tue, 08 Jul 2014 19:34:00 -0000 [thread overview]
Message-ID: <19B9F8D8-7FD6-4A7B-AC83-BBF8D152319D@Denis-Excoffier.org> (raw)
In-Reply-To: <20140707110714.GJ1803@calimero.vinschen.de>
On 2014-07-07 13:07, Corinna Vinschen wrote:
>
> For enumerating a non-primary domain, I get exactly two calls to
> cyg_ldap::open which actually do a connect. The first call opens the
> domain for enumeration. The second call opens the primary domain (NULL)
> to fetch the POSIX offset value for the foreign domain (see my document
> explaining the POSIX offset stuff), unless the application or one of
> its parent processes already fetched the POSIX offset for this domain.
>
> I don't observer any further calls to connect in this scenario.
>
>
In your preliminary documentation (your message dated 2014-06-25, please
correct "seet" in it), trustPosixOffset is "some arbitrary 32 bit value",
ie including 0.
In your code (fetch_posix_offset), td->PosixOffset is used to record the
value and also (when 0) to record that the value has still not been
fetched.
I have encountered this case in real life. The domain admins have set
the trustPosixOffset of the secondary domain to zero. This value is therefore
never recorded and the cldap->open occurs again and again.
Hope this helps.
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 prev parent reply other threads:[~2014-07-08 19:34 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
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 [this message]
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=19B9F8D8-7FD6-4A7B-AC83-BBF8D152319D@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).