From owner-freebsd-bugs Mon Jul 23 10: 0:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4F07C37B405 for ; Mon, 23 Jul 2001 10:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6NH03T91145; Mon, 23 Jul 2001 10:00:03 -0700 (PDT) (envelope-from gnats) Date: Mon, 23 Jul 2001 10:00:03 -0700 (PDT) Message-Id: <200107231700.f6NH03T91145@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Barcroft Subject: Re: conf/13775: multi-user boot may hang in NIS environment Reply-To: Mike Barcroft Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR conf/13775; it has been noted by GNATS. From: Mike Barcroft To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: conf/13775: multi-user boot may hang in NIS environment Date: Mon, 23 Jul 2001 13:10:03 -0400 Adding to Audit-Trail. ----- Forwarded message from Mikhail Teterin ----- Delivered-To: mike@freebsd.org Date: Mon, 23 Jul 2001 11:17:52 -0400 (EDT) From: Mikhail Teterin Subject: Re: conf/13775: multi-user boot may hang in NIS environment To: mike@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org, billf@FreeBSD.org In-Reply-To: <200107210145.f6L1jhH60693@freefall.freebsd.org> On 20 Jul, mike@FreeBSD.org wrote: > Synopsis: multi-user boot may hang in NIS environment > > State-Changed-From-To: open->feedback > State-Changed-By: mike > State-Changed-When: Fri Jul 20 18:45:25 PDT 2001 > State-Changed-Why: > > Does this problem still occur in newer versions of FreeBSD, > such as 4.3-RELEASE? Well, I suppose it does. I don't think, the loud calls for PR closing implies they need to be handled like this... The problem description, I believe, is pretty clear -- until the NIS-client is started before the syslogd, the syslogd will hang trying to figure out the port number of the syslog service (if the services database is NIS-distributed). And the glimpse over /etc/rc and /etc/rc.network shows that it is still the case. Then, of course, since I left the company where I observed the problem well over a year ago, I can not confirm this 100%. Only 99... Bill, now that Mike brought this up, may be, you, who were bitten by this "a few times" too, can arrange for moving of the NIS-stuff from network_pass2 to network_pass1? > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=13775 -mi ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message