This is the mail archive of the
mailing list for the Cygwin project.
Re: ssh logon failure
- From: greenspan <daniel dot greenspan at jhuapl dot edu>
- To: cygwin at cygwin dot com
- Date: Mon, 11 Nov 2013 16:23:15 -0800 (PST)
- Subject: Re: ssh logon failure
- Authentication-results: sourceware.org; auth=none
- References: <4FCF00EB dot 2070600 at gmail dot com> <loom dot 20120607T103956-836 at post dot gmane dot org> <4FD07C1D dot 5070909 at gmail dot com> <loom dot 20130807T185544-35 at post dot gmane dot org> <52028508 dot 7000102 at cygwin dot com> <loom dot 20131025T023724-855 at post dot gmane dot org> <5269D1AA dot 5010306 at cygwin dot com>
Furthermore, I've just discovered that I _can_ log in as the cyg_server user!
>From there, if i attempt to su to myself (user greendg1), I see this:
$ su - greendg1
su: warning: cannot change directory to //APLFS01/GREENDG1$: Not a directory
mkdir: cannot create directory `//APLFS01': Read-only file system
//APLFS01/GREENDG1$ could not be created.
Setting HOME to /tmp.
This utterly confuses me; I know what APLFS01 is, but not why it's part of
this horrible mix... I'm guessing that I have an environment variable
problem, and that depending upon how I log in and when, the environment is
improperly set, which is causing bash to fail, which is why I get the
"operation not permitted" error. But this is all conjecture.
What variable contains the value that bash uses (or ssh or su pass to bash)?
View this message in context: http://cygwin.1069669.n5.nabble.com/ssh-logon-failure-tp57002p104252.html
Sent from the Cygwin list mailing list archive at Nabble.com.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple