public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mirko Vukovic <mirko.vukovic@gmail.com>
To: cygwin@cygwin.com
Subject: mintty startup message: /sbin/nologin: No such file or directory
Date: Sat, 21 Mar 2015 04:05:00 -0000	[thread overview]
Message-ID: <CAO73BABq1D5fUhJYcdc1J5-gP_0NRu3Z5LBcR6NKPbk0bpuc2g@mail.gmail.com> (raw)

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

             reply	other threads:[~2015-03-21  2:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21  4:05 Mirko Vukovic [this message]
2015-03-21  6:45 ` Andrey Repin
2015-03-21 16:41 ` Habermann, David (D)
2015-03-21 16:47   ` Corinna Vinschen
2015-03-23  7:40     ` Habermann, David (D)
2015-03-23 19:17     ` Linda Walsh
2015-03-21 20:03 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO73BABq1D5fUhJYcdc1J5-gP_0NRu3Z5LBcR6NKPbk0bpuc2g@mail.gmail.com \
    --to=mirko.vukovic@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).