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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=mtcxQGffynMKxrko
	kORlNhC56LRjo7+wwd+UqG6+3Ac+u+13YdqsuQpxMp2HhxjwT1OtibxiCyTQGreG
	jpX1HWSFU9jL84aVq2RM6j4Q6KtweNQuSYHcP3lSrtBqzPvwJR7Y+fcFhF5jfQXl
	g68oI8mDd7FrVeBp4jryOWwBkcI=
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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=7P6Bw8x9eaKDOWIJTU15cO
	v0tg0=; b=ectOsjGmFW9zed22rxffnrZcI5tMQeqBnUfQnekYrBMZbizZzMqH76
	VhaeeYoZQo0Pz/3gFyR39GlE21xOPzIKyFgPv3xC4IyXWLTlCgnEsd4bZlZw9yDF
	kxf96OcYXVl02zYgUlCPQ9PSg/hZ/hiij5I4f8RvoVzelOebs4Gu4=
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=-4.0 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Tue, 28 Oct 2014 00:06:39 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<1141638995.20141028000639@yandex.ru>
To:	"Habermann, Dave (DA)" <DAHabermann AT dow DOT com>, cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.1
In-Reply-To:	<C9D37D92E903B347A31B9CF82643BA28072FFFD5@046-CH1MPN1-043.046d.mgd.msft.net>
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
X-IsSubscribed:	yes

Greetings, Habermann, Dave (DA)!

> 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 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?  However, the SECOND
> process and all subsequent ones seem to start significantly faster than before (THANKS FOR THAT!).

If you are using cygserver (from your message, this appears to be the case),
this is expected behavior, given your present conditions.

> 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?

That wouldn't make a change in case of services. Facility provided by
cygserver is optional, and any process that did not succeed to locate
cygserver, will fall back to request the data directly from domain controller.

However, if you have a periodic cron job running fairly often, running
cygserver will likely speed up its startup process. But again, there's no
long-time gains from specifying startup order.

> If so, what would be the preferred way to create such a dependency/startup timing?
> Would a service dependency be sufficient?

Yes. Service dependency will be sufficient, if you find it necessary.
I would also make sure, that cygserver/sshd depends on TCPIP and AFD services.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 27.10.2014, <23:01>

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

- Raw text -