Hi, Tobias On Wed, May 20, 2009 at 7:18 AM, Tobias Fendin <[email protected]> wrote: > > Does the child really die? I did a little test: > > # /etc/rc.d/sshd status > sshd is not running. > # nc -l 22 >/tmp/ssh_test & > [1] 1733 > # /etc/rc.d/sshd start > Starting sshd. > # /etc/rc.d/sshd status > sshd is running as pid 1740. > # ssh someu...@localhost // This didn't timeout or > anything, just didn't give any output. I killed it after a couple of > minutes. > ^C > [1]+ Done nc -l 22 > /tmp/ssh_test > # ssh someu...@localhost > The authenticity of host 'localhost (::1)' can't be established. > DSA key fingerprint is 9f:fa:ee:f5:39:c5:de:c4:8f:b9:c5:43:d8:9d:85:23. > Are you sure you want to continue connecting (yes/no)? ^C > # uname -a > FreeBSD asator 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Thu Mar 5 03:16:15 > CET 2009 r...@asator:/usr/obj/usr/src/sys/A_KERNEL i386 > > As you can see, the first execution of ssh connects to nc (which terminated > when I killed the ssh client). And the second execution it gets through to > sshd (thus, sshd never failed at it's startup). > I don't know if this is the expected behavior, or if it has changed on > -CURRENT. >
Perhaps sshd is checking for forked processes of itself, but not other daemons listening on that socket? -- Glen Barber _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[email protected]"
