Greetings, Corinna Vinschen! > 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. I'd say it again, "sane defaults are better, than alot of options". 1 second to CONNECT to domain server is more than enough time under normal circumstances (for comparison, default DNS _roundtrip_ timeout is 2 seconds, that for a whole conversation sequence). Leave the connect timeout short, and if certain users are unable to cope with slow connections to their domain controllers, they can use less pre-caching, or switch to local files to speed up uid/gid resolution. -- WBR, Andrey Repin (anrdae...@yandex.ru) 03.03.2014, <18:40> Sorry for my terrible english... -- 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
