This is the mail archive of the
mailing list for the Cygwin project.
RE: Testers needed: New passwd/group handling in Cygwin
- From: "Andy Hall" <fixpertise-consulting at comcast dot net>
- To: <cygwin at cygwin dot com>
- Date: Mon, 3 Mar 2014 09:24:50 -0800
- 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>
> On Mar 2 14:20, Frank Fesevur wrote:
> > 2014-02-28 22:08 GMT+01:00 Corinna Vinschen:
> > > That's not really a problem but a case of "it is as it is". To get the
> > > user and group info, Cygwin has to contact the DC and/or GC and then
> > > runs into a timeout. Right now, the LDAP timeout is set to 3 seconds.
> > > I don't know yet if it's such a bright idea to lower this timeout value.
> > I understand why it happens. And three seconds are not the problem.
> > It is just a bit confusing to activate the shortcut and for 3 seconds
> > nothing seems to happen. First time I double-clicked again because I
> > though it wasn't working at all. Obviously a bit later two terminal
> > showed up. If mintty would should up empty and "wait" those three
> > seconds before something happens it is more clear it just takes some
> > startup time. But maybe that is more a mintty problem.
> No, this is not mintty's fault. You have to understand that the
> request for information from the DC is called before the actual
> application had any chance to initialize, This happens before
> the application has, in fact, been called from the Cygwin DLL.
> Therefore, if the three seconds are a burden, there are three choices
> going forward:
> - We reduce the timeout to 1 second in general, which could be a problem
> when utilizing a slow VPN conncetion to the DC,
> - We allow the user to specify a timeout value and set the default to
> 1 second.
> - We stick to the 3 seconds and users should switch to files (/etc/passwd
> /etc/group) when being offline from their DC.
> I'm really not sure what the best way is, I guess we as a community have
> to dice this out somehow.
Why not have a command that allows you choose whether or not you are "on-line", that is, currently connected to a
network with a DC or "off-line" where you are not. In the former you consult the DC in the latter you use the local
files? That way you can leave the timeout at a reasonable value.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple