From owner-freebsd-bugs@FreeBSD.ORG  Wed May 20 14:50:03 2009
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9FB961065673
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 20 May 2009 14:50:03 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 8C87F8FC19
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 20 May 2009 14:50:03 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4KEo3sD061400
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 20 May 2009 14:50:03 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4KEo3kn061399;
	Wed, 20 May 2009 14:50:03 GMT (envelope-from gnats)
Date: Wed, 20 May 2009 14:50:03 GMT
Message-Id: <200905201450.n4KEo3kn061399@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Dimitry Andric <dimitry@andric.com>
Cc: 
Subject: Re: bin/134694: gives false-positive when unable to obtain socket
 [WAS: sshd(8) - alert user when fails to execute from rc.d]
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dimitry Andric <dimitry@andric.com>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2009 14:50:03 -0000

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". :)