From owner-freebsd-hackers@FreeBSD.ORG Wed May 20 14:46:10 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE2F6106564A; Wed, 20 May 2009 14:46:10 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id AD15B8FC17; Wed, 20 May 2009 14:46:10 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:8d33:c8ee:aff8:342] (unknown [IPv6:2001:7b8:3a7:0:8d33:c8ee:aff8:342]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D222A5C42; Wed, 20 May 2009 16:46:09 +0200 (CEST) Message-ID: <4A1417B3.3030303@andric.com> Date: Wed, 20 May 2009 16:46:11 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b5pre) Gecko/20090515 Shredder/3.0b3pre MIME-Version: 1.0 To: Glen Barber References: <4ad871310905181949s2874795eoa5ddf425746310bf@mail.gmail.com> <4A13E180.1040606@andric.com> <4A13E6F7.7070309@glocalnet.net> <4A13E906.7020907@andric.com> <4ad871310905200740n744f9b83j96db2a3c1a6bec43@mail.gmail.com> In-Reply-To: <4ad871310905200740n744f9b83j96db2a3c1a6bec43@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 14:46:11 -0000 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". :)