DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=DGeXUPnxRotj2SmBvkhdKcHsNlhPu
	DwG2Gq6mZIRkq5LoHV43Hxe5NJvM9AOWkER0FqFRPGwzzjXrA2SRxb6mQkh5c2KJ
	fGrqYob026ZWnVUY5cQvMtE2WyfSv9sYujQkGJTphAkDoKx0DtPofDEtgEUXWly9
	AGeO2KQYzcjttM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Habermann, David (D)" <DAHabermann@dow.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: mintty startup message: /sbin/nologin: No such file or directory
Date: Sat, 21 Mar 2015 20:03:40 +0000
Message-ID: <C9D37D92E903B347A31B9CF82643BA28074B2151@046-CH1MPN1-042.046d.mgd.msft.net>
References: <CAO73BABq1D5fUhJYcdc1J5-gP_0NRu3Z5LBcR6NKPbk0bpuc2g@mail.gmail.com> <C9D37D92E903B347A31B9CF82643BA28074B1ED6@046-CH1MPN1-042.046d.mgd.msft.net> <20150321164125.GB15431@calimero.vinschen.de>
In-Reply-To: <20150321164125.GB15431@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Received-SPF: None (protection.outlook.com: dow.com does not designate permitted sender hosts)
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2015 20:03:41.6391 (UTC)
X-MS-Exchange-CrossTenant-Id: c3e32f53-cb7f-4809-968d-1cc4ccc785fe
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=c3e32f53-cb7f-4809-968d-1cc4ccc785fe;Ip=[65.52.44.158];Helo=[mail.bsnconnect.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0101MB1184
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id t2LK417n004715


>LDAP can't have to do with that, in theory.  The whole mechanism should give a sane result even if LDAP >connections fail, because the core part is the call to LookupAccountSid and that's the only call which has to >succeed.

Certainly my speculation of the cause is exactly that....speculation.  My observations, however, are sound and very reproducible on my machine.  If cygserver starts up rapidly after boot the result is not desirable, whereas if cygserver start up is delayed (either done manually or via delayed service startup), then the result is good.

I'll be happy to do any testing you might like on Monday, but this weekend is a busy one for me so I likely won't be able to do much until the work-week.

Dave