X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=DKEUx0QKwoUJ1SToWjc2wXZji2s/vLzbPKJ65Wl/TwLPG+xRP+9FM
	M72q5ugo12J+BgFLpkyxpXezy5UqTmPNZAT+hCLifDMIVZBa98EG7xkzROSnpi5t
	BYHQF0BkQCzGvWMBF0bJ79ClJWo3LP25aHaLe1dYRr2IQueVZov+0A=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=VVD7938ScOYsE5mE9/b6fzBsprM=; b=X3a8BtZhMWaWvyjO6u6VEsKhQbsM
	7Dw+rPh+MhzeTvgvoWlMFEds7FV5nDNMMwj1wRYMUexhlLQPEbh9NXv16EIPBifq
	1nEL6xsyOAILgvxUaJ9HgZCCAJ1GrH5gRsuQmtFZFGkUFFXZEDmwIyKnocstFE+f
	89R8rhkUos9oJRw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 27 Oct 2014 22:26:37 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
Message-ID:	<20141027212637.GZ20607@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<announce DOT 20141022092323 DOT GH32374 AT calimero DOT vinschen DOT de> <C9D37D92E903B347A31B9CF82643BA28072F9229 AT 046-CH1MPN1-043 DOT 046d DOT mgd DOT msft DOT net> <20141022135424 DOT GB18857 AT calimero DOT vinschen DOT de> <C9D37D92E903B347A31B9CF82643BA28072FFFD5 AT 046-CH1MPN1-043 DOT 046d DOT mgd DOT msft DOT net>
MIME-Version:	1.0
In-Reply-To:	<C9D37D92E903B347A31B9CF82643BA28072FFFD5@046-CH1MPN1-043.046d.mgd.msft.net>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--PyWBHxIrsGpYNMFw
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 27 18:35, Habermann, Dave (DA) wrote:
> Loaded the test release here today and found that it seems to work as
> expected, both without the /etc/nsswitch.conf file (operates as
> before) and with both passwd and group set to "db" in the file.  Only
> two slightly negative observations I've made so far are 1) ps -ef only
> allows for 8 character UIDs, and thus longer UIDs (for example
> MyMachine+cyg_server) don't show up well

This was already a problem for some time.  I have a look into fixing this.

> and 2) the very first cygwin
> process I start seems to take a bit longer to start up now (in either
> mode) than before (7-10 seconds depending on the contents of
> nsswitch).  Perhaps this is possibly due to the fact that I'm
> accessing AD at some distance over a VPN?

This is very likely.  For this scenario it might make a lot of sense
to run cygserver, see the docs for this.

> However, the SECOND process
> and all subsequent ones seem to start significantly faster than before
> (THANKS FOR THAT!).

You're welcome :)

> Question:  In the documentation you indicate that "If cygserver is
> running it will provide passwd and group entry caching for all
> processes in every Cygwin process tree started after cygserver."
> Normally I have several processes (specifically sshd, cygserver, cron
> and httpd2) automatically start up as services when my system boots
> up, and I have not specified the order.  Would it now be desirable to
> have cygserver starting up first, followed by the others?  If so, what
> would be the preferred way to create such a dependency/startup timing?
> Would a service dependency be sufficient?

Now that you mention it... yes, a service dependency might be helpful.
Unfortunately it's tricky to automate this.  Is it possible to add
service deps after having installed a service?

> Thanks again for your efforts on this!

I'm glad if you like it,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--PyWBHxIrsGpYNMFw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUTriNAAoJEPU2Bp2uRE+g6vYP/318a2s2EfFw/OaeDoMvuPUW
1C4X8Oj/pr9piMlyZuzLP38ixXCrMDANusRz6ZsEeyfY6vVHAE5Z1nyJ9wIf1dNZ
JTuL5JeU+7P38TAuU/BJjwuT45AcHLaBs+B7YK2sEz88TVrQyevFUQLggVj8vGKK
5i3fSUCyKJWoKfCDW2MZZND+FH/jjlQ77kQtnOsezrmpZfUAmG8JaSLzImpU+JwY
tfS9KZHBaHlebW6lN4FER/PsZuoDj5JrTLpyacFRbVu2HgXpahLg+wGbj99lcyYr
JPMu/EKroVuB19MfRXWrg/ue0yYptJ/i/YHRcIH/K9+P5CG/c+f/xktB/RKF1qCB
sxUKcjXFh4Ze3UN16s/zhIidZ/gKXa66bKgVFHfFkSTxLnI5RpP7SA0TULULSdJa
Y5Plq6gy6hqKPI98gdmsEg6BH0VIuPKQv2541TreUhXqMWcyOZa+xZRD1pbzuSuK
rWVQgppYKYvyib9cmwI68aCiRm9w8g/ec4v/TDGpxIQ4sCEE+kCLJSTD1liyYSGF
YORkqpjl/vp0L7L4qOy7UByIauXGuYev9nDzoxx6je+8IGSlIy49Ea0kgFUQiKO5
0a+s+1BHtDNaARuPo5NTPh3syULQizb52zH9he5v7RebzE0ODVwavCVSLDyjq2LP
SB+Zqwo9SOyV5AoDtwuo
=Fd9/
-----END PGP SIGNATURE-----

--PyWBHxIrsGpYNMFw--

- Raw text -