This is the mail archive of the
mailing list for the Cygwin project.
Re: Administrator lacking super-user privileges on cygwin installation
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Cc: Ville Herva <vherva at niksula dot hut dot fi>
- Date: Tue, 05 Aug 2003 11:31:54 -0400
- Subject: Re: Administrator lacking super-user privileges on cygwin installation
- References: <Pine.GSO.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
Igor Pechtchanski wrote:
On Tue, 5 Aug 2003, Ville Herva wrote:
On Mon, Aug 04, 2003 at 10:03:18PM -0400, you [Larry Hall] wrote:
I tried adding '-d' to the sshd parameters, but that doesn't help (gives
same error 255) - it seems to die earlier than that.
What does /var/log/sshd.log say?
It remains empty, on both servers.
Based on time stamp, it appears to last touched when I ran sshd from command
line. As said, now the sshd is running as a service on an user account. With
SYSTEM account, service still fails to start with error code 255. I believe
sshd fails to _execute_ for some curious reason (so it doesn't get to open
the log), but why?
IIRC, the default installation of sshd as service used the event log for
all output, rather than /var/log/sshd.log (though I'm not too sure on this
Right. But Ville mentioned that he ran sshd with the '-d' flags which
would send diagnostics to /var/log/sshd.log.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html