From owner-freebsd-rc@FreeBSD.ORG  Fri Feb 10 23:42:39 2012
Return-Path: <owner-freebsd-rc@FreeBSD.ORG>
Delivered-To: freebsd-rc@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 981A9106567C
	for <freebsd-rc@FreeBSD.org>; Fri, 10 Feb 2012 23:42:39 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 172-17-150-251.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 1443BB4462;
	Fri, 10 Feb 2012 23:41:55 +0000 (UTC)
Message-ID: <4F35AB43.9020704@FreeBSD.org>
Date: Fri, 10 Feb 2012 15:41:55 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
	rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Jilles Tjoelker <jilles@stack.nl>
References: <4F322437.5030100@FreeBSD.org> <20120208230852.GA83950@stack.nl>
	<4F33031E.7000507@FreeBSD.org> <20120210110356.GA6723@stack.nl>
In-Reply-To: <20120210110356.GA6723@stack.nl>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-rc@FreeBSD.org
Subject: Re: Bringing sanity to the RPC/NFS related scripts
X-BeenThere: freebsd-rc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion related to /etc/rc.d design and implementation."
	<freebsd-rc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-rc>
List-Post: <mailto:freebsd-rc@freebsd.org>
List-Help: <mailto:freebsd-rc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 23:42:39 -0000

On 02/10/2012 03:03, Jilles Tjoelker wrote:
> Hmm, so statd sometimes does not feel like starting the first time, but
> is willing the second time? That would be a bug that should not be
> worked around with that extra check.

It seems to be related to the first random port that statd chooses being
in use, and statd not being very smart about recovering from that. (And
yes, I know about the -p option .... not really the point.) I'd like to
be able to thoroughly test that all required services are running when
the next thing on the list is starting.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/