This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-002
- From: Warren Young <wyml at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 9 Dec 2014 15:05:47 -0700
- Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-002
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 20141206194943 dot GD3810 at calimero dot vinschen dot de> <6695DB56-B38C-4FC4-A58A-9CE8798DBAFB at etr-usa dot com> <20141209105617 dot GF3810 at calimero dot vinschen dot de>
On Dec 9, 2014, at 3:56 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Dec 8 15:14, Warren Young wrote:
>> On Dec 6, 2014, at 12:49 PM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>>
>>> - Cygwin can now generate passwd/group entries directly from Windows
>>
>> don’t use AD here, and /etc/passwd suffices
>> for my purposes
>
> You can still benefit, I hope. Even when using only the local SAM, the
> process startups should be a tad bit faster than when every exec'ed
> process has to read /etc/passwd and /etc/group files:
Challenge…accepted.
I decided to do the nastiest thing I could think of to Cygwin: run a configure script. ;)
In my Windows 10 Technical Preview test VM, Cygwin 64 1.7.33 runs the iperf3 configure script in 20 seconds. On upgrading to 1.7.34-002, without doing anything to nsswitch.conf, the time remained the same. On making the suggested change to nsswitch.conf, configure time went *up* to 21 seconds.
So, I moved the new nsswitch.conf back out of the way, relaunched MinTTY, and configure time dropped its extra second.
Hmm.
--
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