Re: bin/134694: gives false-positive when unable to obtain socke

The following reply was made to PR bin/134694; it has been noted by GNATS.

From: Dimitry Andric <dimitry@andric.com>
To: Glen Barber <glen.j.barber@gmail.com>
Cc: hackers@freebsd.org, bug-followup@freebsd.org
Subject: Re: bin/134694: gives false-positive when unable to obtain socket
 	[WAS: sshd(8) - alert user when fails to execute from rc.d]
Date: Wed, 20 May 2009 16:46:11 +0200

 On 2009-05-20 16:40, Glen Barber wrote:
 > sshd was listening on :25, both IPv4 and IPv6
 > sendmail was listening on :25 (because I had forgotten to disable it)
 > 
 > The system boots, and sendmail starts before sshd.  When sshd starts
 > (or tries to) there is no console output that it had failed.  The only
 > way you realize it is not running, is when you cannot remotely log in.

 Yes, this is unfortunate, but normal, as I explained in an earlier post.

 The sshd process does not return any error (and thus the /etc/rc.d
 script doesn't either), because it has no way to know that its forked
 copy died.

 The solution to this PR is "don't run stuff on conflicting ports". :)
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"