This is the mail archive of the
mailing list for the Cygwin project.
RE: Very slow Cygwin startup on Windows 7
- From: "Dennis Hagarty (dehagart)" <dehagart at cisco dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 11 Feb 2015 21:39:21 +0000
- Subject: RE: Very slow Cygwin startup on Windows 7
- Authentication-results: sourceware.org; auth=none
- References: <3FEEC3A37A0B0A48AA326075128C32EE4DC9F0E8 at xmb-rcd-x01 dot cisco dot com> <87mw4nugdx dot fsf at Rainer dot invalid> <3FEEC3A37A0B0A48AA326075128C32EE4DC9F137 at xmb-rcd-x01 dot cisco dot com> <869208266 dot 20150210030528 at yandex dot ru>
I'll do that.
I see the purpose of the update - just the way it was documented didn't really make
it clear to me that it was going to hit my DC and cause performance issues.
The UID stuff doesn't really worry me too much, I was happy with the old way.
But I'll use your suggestion tomorrow.
From: Andrey Repin [mailto:firstname.lastname@example.org]
Sent: Tuesday, 10 February 2015 01:05
To: Dennis Hagarty (dehagart); email@example.com
Subject: Re: Very slow Cygwin startup on Windows 7
Greetings, Dennis Hagarty (dehagart)!
>>> Well, nsswitch.conf was a good suggestion - I'd left it as the default
>>> (which is empty), but I added a 'files' entry and it came good again.
>>> Changing the passwd and group entries to 'files db' makes it very slow
>>Limit the number of entries that Cygwin fetches from the DC. Also,
>>starting a cygserver would help.
>>> Not sure what changed here, I have a very good connection to my DC,
>>> but obviously something wrong here now.
>>You may be surprised at how slow a DC really can be when it sees some
>>load, regardless of connection speed when you try to fetch several
>>thousand entries. If I were to try a 'mkpasswd -d' on our DC I'd
>>usually have to wait about an hour with very little network traffic to
>>show (the resulting file would be about 4MiB).
> Thanks Achim - I've recreated my passwd and group files to be sure.
> I checked some domain lookups and they take a second or two for each entry - quite slow.
> So, I'll leave nsswitch where it is for now and I've started cygserver.
If you are accepting suggestions, and up for some experimentation, try this:
# getent passwd $(id -u) > /etc/passwd
# getent group $(id -G) > /etc/group
# echo -e "#\npasswd: files db\ngroup: files db\n" > /etc/nsswitch.conf
and start bash without cygserver running. Just for test.
The idea is to have "your" groups in files so that in simple case of (just
startup" Cygwin don't have to talk to DC all too much. If at all.
You'd still need to run cygserver to benefit from long-time caching, though.
> But I'm just wondering how this failed after I updated - I was using it
> successfully 30 mins previously.
> I've had it configured this way for years.
That was the sole point of the update. :) No, no. Not the snail's speed, ofc.
But the more direct connection of Cygwin to the native security environment.
File ACL's included.
Andrey Repin (firstname.lastname@example.org) 10.02.2015, <02:54>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple