From owner-freebsd-bugs@FreeBSD.ORG  Mon Jan  4 10:35:58 2010
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 9918E1065698;
	Mon,  4 Jan 2010 10:35:58 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 6F4768FC18;
	Mon,  4 Jan 2010 10:35:58 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o04AZw5f039806;
	Mon, 4 Jan 2010 10:35:58 GMT
	(envelope-from gavin@freefall.freebsd.org)
Received: (from gavin@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o04AZw7a039802;
	Mon, 4 Jan 2010 10:35:58 GMT (envelope-from gavin)
Date: Mon, 4 Jan 2010 10:35:58 GMT
Message-Id: <201001041035.o04AZw7a039802@freefall.freebsd.org>
To: tonys@stg-stl.com, gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	gavin@FreeBSD.org
From: gavin@FreeBSD.org
Cc: 
Subject: Re: conf/72592: [nis] NIS Domain Master fails as client of itself
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Mon, 04 Jan 2010 10:35:58 -0000

Synopsis: [nis] NIS Domain Master fails as client of itself

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Mon Jan 4 10:33:26 UTC 2010
State-Changed-Why: 
To submitter: I suspect this was fixed several years ago, with the introduction
of the new rc.d boot framework.  It appears that now at least, ypbind will
always start after ypserv, so should be available on boot.

Are you able to confirm that this is the case?


Responsible-Changed-From-To: freebsd-bugs->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Mon Jan 4 10:33:26 UTC 2010
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=72592