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=jfm9IHeoe2DMiplb67S0sUvk0lASg
	/zirQc2Dmvip4WRMC7S6tn3tRzLEhb9Bh2PPkwwZ/utHnyBqK+RZfScB0epnMqFO
	SvwKbem0tk/iNBBr9ohJkEkLYRr+x+jbbGbX9LnlpMZ0KWar+9jGlxvxb9O4diD3
	TQ7HoOdW/mdj9o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: "Habermann, David (D)" <DAHabermann AT dow DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: mintty startup message: /sbin/nologin: No such file or directory
Date: Sat, 21 Mar 2015 13:50:38 +0000
Message-ID: <C9D37D92E903B347A31B9CF82643BA28074B1ED6@046-CH1MPN1-042.046d.mgd.msft.net>
References: <CAO73BABq1D5fUhJYcdc1J5-gP_0NRu3Z5LBcR6NKPbk0bpuc2g AT mail DOT gmail DOT com>
In-Reply-To: <CAO73BABq1D5fUhJYcdc1J5-gP_0NRu3Z5LBcR6NKPbk0bpuc2g@mail.gmail.com>
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 13:50:39.7217 (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: DM2PR0101MB1182
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id t2LDp0wY012582

I observed the same error.  In my case, it was apparently caused by a too-rapid startup at boot of cygserver, which apparently could not connect to LDAP at that early stage.  If I prevented any of my Cygwin services from starting at boot, and then started them manually once I logged in, the problem was not observed.  My current solution (still perhaps not the best) is to set all of my Cygwin services to start as "Automatic (Delayed Start)" in the services control panel.  This does solve my problem, but causes about a 1-2 minute delay in the availability of sshd/httpd2 after a reboot.

NOTE: I've also set all of my other Cygwin services to be dependent on cygserver as described in the Cygwin documentation.

Dave
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Mirko Vukovic
Sent: Friday, March 20, 2015 10:14 PM
To: cygwin AT cygwin DOT com
Subject: mintty startup message: /sbin/nologin: No such file or directory

Hello,

after upgrading cygwin64 on my company laptop, mintty gives the following message *when connected to the network from home*:

/sbin/nologin: No such file or directory

Pressing enter closes the window.

I can start bash from Windows' command window.  From there, I see that there is no /sbin/nologin file, heck there is no /sbin either.

A couple of data points:
- After the upgrade, I renamed away the /etc passwd and group files.
- I was able to open mintty while connect to the network at work


I have an almost identical setup on my other windows 7 desktop (always connected to the network) that does not exhibit this problem.

I saw some posts from 2011 about creating my own file but I am puzzled as to why I see this on my laptop and not on my desktop.

I looked in Windows logs and saw nothing.  I saw nothing in /var/log

Thanks,

Mirko

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