RE: [ssh-l] Running OpenSSH as a service (revisited)

That was a pretty good idea, although I'm not sure the results turned out
to be very helpful,
but maybe they are... I tried and got the following:

C:\WINNT\system32>c:\cygwinnt\usr\sbin\sshd -D -d -d -d
/etc/sshd_config: No such file or directory

So after some testing.. what I did was, copied c:\cygwinnt\etc to c:\etc and
tried again:
C:\cygwinNT\etc>c:\cygwinnt\usr\sbin\sshd -D -d -d -d
debug1: sshd version OpenSSH_3.1p1
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.

So it looks like it worked via services after I did that...
But, when I try to do it from cygrunsrv, I still get:

admin@PEGASUS ~
$ cygrunsrv -S sshd
cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062:
The service has not been started.

Oh, and yes, I'm using the latest cygwin, cygrunsrv, and latest openssh for
cygwin as well.

Any other suggestions? Thanks.

At 10:39 AM 3/8/2002, you wrote:
>Try starting it manually from within a SYSTEM-launched
>command prompt window, in verbose mode, to see what error
>messages appear.
>
>1. Start, Run, cmd.exe
>2. Type the command line at 14:25 /interactive cmd.exe
> (change 14:25 to 2 minutes ahead of current time)
>3. A window titled "...\MSTask.exe" should appear in <2 min's
> Edit the window's Layout properties:
> Screen Buffer Size-Height=999
> Window Size-Height=40
> Save for either current or all sessions
>4. In this window, type "c:\cygwin\usr\sbin\sshd -D -d -d -d"
> If it fails, look for error/failure/access denied messages
>
>If you haven't already, update your Cygwin files to the latest;
>that fixed some problems that might be related to your errors.
>
>(It also broke (fixed?) my systems-My users were in group 513
>(None/Domain Users), (working fine under 3.02p1-1)
>and I had to change them to something else
>(I used 544, Administrators) because I got setgid
>failures for gid 513 under 3.1p1-1...I had to run
>fixperms.sh again after I changed the user entries
>in /etc/passwd. All is well again...Now my pubkey
>authentication is working-it wasn't before the upgrade.
>It could be because of the gid change, though...
>
>Jim
>

--
List Information: http://tech.erdelynet.com/maillist-ssh-l.asp
List Archives:    http://erdelynet.com/archive/ssh-l/