Thanks, Corinna, for asking if sshd was called with the -D option. This
was the point, although I do not really know why -D was missing (I used
ssh-host-config).
This is was came out before (sshd in fact was running):
$ cygrunsrv -Q sshd
Service : sshd
Display name : CYGWIN sshd
Current State : Stopped
Command : /usr/sbin/sshd
Then I removed the service:
$ sc delete sshd
[SC] DeleteService SUCCESS
Then I rerun the installation script (only selected the service
re-install, of course using the cyg_server account for Win2k3):
$ ssh-host-config
...
*** Info: Host configuration finished. Have fun!
$ cygrunsrv -S sshd
$ cygrunsrv -Q sshd
Service : sshd
Display name : CYGWIN sshd
Current State : Running
Controls Accepted : Stop
Command : /usr/sbin/sshd -D
I guess, when I was installing the service before, I may have changed
something in the Properties menu of the CYGWIN sshd service, perhaps I
tested something under the SYSTEM account and then have reverted to the
cyg_server account, so by this action finally the -D may got lost for the
call of sshd. BTW, I do not actually understand the meaning of -D (When
this option is specified, sshd will not detach and does not become a
daemon. This allows easy monitoring of sshd.)
Thank you again - Ulf-Dietrich
On Thu, 8 Mar 2012, Corinna Vinschen wrote:
That doesn't happen for me. Does your service entry for sshd omit the
-D option? What does `cygrunsrv -Q sshd' print? That should look like:
$ cygrunsrv -Q sshd
Service : sshd
Display name : CYGWIN sshd
Current State : [...]
Command : /usr/sbin/sshd -D
Corinna
On Mar 8 11:21, Ulf-Dietrich Braumann wrote:
Well, while sshd now can be launched again by cygrunsrv, still the
mechanism behaves weird, in the event viewer sshd tells me to be
stopped short after it was started,
--
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
