Mail Archives: cygwin/2005/01/14/11:11:14
Thanks for the reply Dave,
> Anyway, if running as SYSTEM it writes to
> /var/log/sshd.log, but running as an
> ordinary user it fails, then it's almost certainly the case
> that sshd.log is
> owned by SYSTEM user because it was first created by SYSTEM
> user. If that's the
> case "chmod a+rwx /var/log/sshd.log" should help.
Regarding this, I have deleted the 'sshd.log' file that was created when
it ran under the SYSTEM account. I also confirmed that the
'sshd_server' user had write privileges to the /var/log directory. Ie:
touch /var/log/sshd.log under that user created a file that was owned by
'sshd_server'.
I subsequently deleted that file.
> Also, nobody's told Sean to take a look in the windows
> event log yet, and see
> if there was any sign of life there.
The only thing that appears in the event log is the service failure
entries. Nothing of real substance. For example, the following is a
typical entry:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 1/11/2005
Time: 4:39:06 PM
User: N/A
Computer: DCESAP08
Description:
The CYGWIN sshd service terminated unexpectedly. It has done this 3
time(s).
I have auditing turned on for most all 'failures', and of course, there
is nothing in the Security log. File Monitor and Registry Monitor show
nothing significant either.
For now, I created a BAT file to:
Runas /user:sshd_server C:\cygwin\cygwin.bat
Which happily opens a bash shell. I proceed to /usr/sbin/sshd, .. It
returns no errors. I close my bash window.
The service works.
So, this leads me to think something definitely fishy with the
'cygrunsrv' running sshd on this configuration. It's a new server in a
data center running Windows Enterpirse Server 2003..
Thanks for all the help!
-Sean
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -