From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96023 invoked by alias); 21 Mar 2015 16:47:31 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 96011 invoked by uid 89); 21 Mar 2015 16:47:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_50,SPAM_BODY1 autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 21 Mar 2015 16:47:30 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id C15D9A80932; Sat, 21 Mar 2015 17:47:27 +0100 (CET) Date: Sat, 21 Mar 2015 20:03:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: mintty startup message: /sbin/nologin: No such file or directory Message-ID: <20150321164727.GC15431@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="adJ1OR3c6QgCpb/j" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-03/txt/msg00382.txt.bz2 --adJ1OR3c6QgCpb/j Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 709 On Mar 20 22:13, Mirko Vukovic wrote: > Hello, >=20 > after upgrading cygwin64 on my company laptop, mintty gives the following > message *when connected to the network from home*: >=20 > /sbin/nologin: No such file or directory I replied to David's mail, but the same puzzled observations and question for testing apply to your case, of course. So, let me point you at https://cygwin.com/ml/cygwin/2015-03/msg00380.html Let's discuss this further, please. This behaviour isn't nice and I would like to avoid it in the next Cygwin release. Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --adJ1OR3c6QgCpb/j Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVDaCfAAoJEPU2Bp2uRE+g0dcQAIMmMb0Uc20XPD/Tu296s7E5 5n/izGATVgnfF5Wt4iD3WAgD6dG+9o8nBTfSsar6eyzWaEkRKf9UE3JOb7cGbN/M 8b0ACijewrJjUw2UH87UWXNVoP3dus3QeEClW6oV85JwlWk9ozoEm00cXQ1KMeXM irDAvQ5b0OrzzVc7zSKHtTrlB+55yUzFTreUoaHgH8dy7ab45U5aCZzBJFIqF2+D QVyMB6P/sk60earP2c+jk4W0rzqLQ+5Efd8r29LLAtKtdATI7V6FmaK3TSMT+T4F MHgMC4Nlo34+hiBbwohONx2ERzsXucHvU25WLxQw1x0m1Ceb5hA6lFtHJwA9HD0v 3SOGnlBwsTUEmqwLlb1HxHk7VBMjfshiFY7ZBjDP/BGNN24AhAJfWNQfKuM7Ql9Q PS1YWzVJBzqzkJaKMbIgf8WQlOsOjKPok+kAD9ssPtMQCc7+FQ28IL7vNIEz5Rwo eU3kZzrrBnnXF+d7R485FVTq6IZJPzdegRMLRphbAaTTdQByeUb+tYc6PH6pGvJa ARJIQfLbetJQ7RyPMCwT4D4zsjJ2xG8TR4YGF7EYPwDn0f5erc4iM3QXlIvJKtTX Xwak/HS94C5G+swJYxmnCyKhzQukFGqMNEoCCPuMSITJRlFdSs81uW+4C9jGWo31 KY9yEB0GDO3tchMuGp22 =2JJb -----END PGP SIGNATURE----- --adJ1OR3c6QgCpb/j--