On Thu, 16 Sep 1999, Mikhail Teterin wrote:
> When the machine boots, /etc/rc is doing certain things,
> like chown, which fail/hang since ypbind is not running
> In particular, things like chown (needs user and group
> ids), mounting NFS systems (needs host names), syslog
> (needs syslog service from services database).
Amen. This has bitten me a few times too.
- bill fumerola - email@example.com - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - firstname.lastname@example.org - billf@FreeBSD.org -
When the machine boots, /etc/rc is doing certain things,
like chown, which fail/hang since ypbind is not running
In particular, things like chown (needs user and group
ids), mounting NFS systems (needs host names), syslog
(needs syslog service from services database).
Probably, ypbind should go into network_pass1...
A workaround is to put the syslog service into
/etc/services. Change `chown root:wheel' to `chown 0:0'
in /etc/rc and put the NFS servers into /etc/hosts.
This should not be needed...
In our environment, the /etc/services file consists only
of a single `+'. `+:::::::::' follows the list of the
FreeBSD standard "users". `+:::' is the first line of
When such a setup boots, one needs to press ^C and then
start things like syslog manually.
Does this problem still occur in newer versions of FreeBSD,
such as 4.3-RELEASE?
Adding to Audit-Trail.
----- Forwarded message from Mikhail Teterin <email@example.com> -----
Date: Mon, 23 Jul 2001 11:17:52 -0400 (EDT)
From: Mikhail Teterin <firstname.lastname@example.org>
Subject: Re: conf/13775: multi-user boot may hang in NIS environment
Cc: freebsd-bugs@FreeBSD.org, billf@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
> 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
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?
----- End forwarded message -----
This is still a problem. Awaiting fix and committer.
Itouch is always be redirected and it allow https ( safesite)
Sent from my iPod
[crees@pegasus]~% rcorder /etc/rc.d/* | grep -E
'ypbind|devfs|ipfs|mdconfig2|named' /etc/rc.d/ipfs /etc/rc.d/devfs
/etc/rc.d/mdconfig2 /etc/rc.d/named /etc/rc.d/ypbind
The above scripts use chown and run before ypbind, but no longer
including syslogd. devfs and mdconfig only use chown if configured to,
and ipfs only on first running.
The only real one that may cause an issue is named, which we could
probably switch to using 0:0
Do you know if this is still a problem?
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped
This has been in feedback for years.
Closing as OBE.
If someone has a scenario today where this hangs on boot, please open a new bug.