This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Testers needed: New passwd/group handling in Cygwin
- From: Warren Young <warren at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 03 Mar 2014 17:37:05 -0700
- Subject: Re: Testers needed: New passwd/group handling in Cygwin
- Authentication-results: sourceware.org; auth=none
- References: <20140227094951 dot GD2246 at calimero dot vinschen dot de> <loom dot 20140227T134714-188 at post dot gmane dot org> <20140227134632 dot GG2246 at calimero dot vinschen dot de> <765945729 dot 20140228031219 at yandex dot ru> <20140228120748 dot GN2246 at calimero dot vinschen dot de> <87y50vc910 dot fsf at Rainer dot invalid> <20140228201047 dot GC2381 at calimero dot vinschen dot de> <CAKf2h5TjyeMxuw=XkqoGMC8A_f+LpSzcx5nof5ViUBQ-0sYXFg at mail dot gmail dot com> <20140228210804 dot GE2381 at calimero dot vinschen dot de> <CAKf2h5QbafQq25jndf8RdDGWsp_MMfziBep2Pe1H7rA+OmOCdA at mail dot gmail dot com> <20140303092114 dot GA26619 at calimero dot vinschen dot de> <1686957830 dot 20140303195207 at yandex dot ru>
On 3/3/2014 08:52, Andrey Repin wrote:
I'd say it again, "sane defaults are better, than alot of options".
Agreed in principle.
However, observe that all network stacks have a bunch of built-in
timeout options. They're rarely exposed to the user level, but their
defaults are typically quite high. (e.g. 60 seconds for connection
timeout.) Over the past 3 decades of TCP/IP, we've discovered that
networks are weird.
for comparison, default DNS _roundtrip_ timeout is 2 seconds,
The typical DNS transaction is just 2 UDP packets, one each direction:
query and response.
I tested a simple, unencrypted LDAP login-and-drop-conn transaction here
against a real production AD server, and it required 8 packets, 5 of
which were TCP/IP connection establishment and shutdown.
Add in the encryption, authentication, and authorization overheads of a
"real" LDAP query, and it could go up to dozens of packets.
That said, it only took about 1 ms to my simple test. The AD server was
on the other side of a router, on a fast WAN.
Someone testing this new cygwin1.dll in a domain environment[*] should
do a packet capture of what Windows sends when the DLL does its new thing.
The captured data isn't terribly interesting here. What we want to know
is how many packets it takes, and what the timestamps are on the
captured frames. Most especially, the delta between the first and last
packets, but if there are any significant time gaps, that could be
interesting, too.
[*] Not me. The only reason we have any AD around here at all is for
testing software that authenticates users against third party AD servers.
--
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