Bug 20420

Summary:	When NIS client enabled machine doesnt boot correctly a line in /etc/rc doesnt work?!
Product:	Base System	Reporter:	yurtesen <yurtesen>
Component:	conf	Assignee:	Dag-Erling Smørgrav <des>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.1-STABLE
Hardware:	Any
OS:	Any

Description yurtesen 2000-08-05 00:50:01 UTC

When I have nis_client_enable="YES" in my /etc/rc.conf file the boot process is haning at line
chown root:wheel /dev/tty[pqrsPQRS]*
of the /etc/rc file when I comment out this line the machine boots correctly. The same happened in 2 different machines I use here.
Somebody may lock out himself when rebooting the machine or they might need to go to system room to press ctrl-c to cancel chown and continue booting. After a power failure machines would not boot correctly! So this is kinda serious problem I guess... ?

Fix: 

I dont know yet but if you know something please let me know.
yurtesen@ispro.net.tr
How-To-Repeat: put
nisdomainname="!DOMAINNAMEHERE!"
nis_client_enable="YES"
in your /etc/rc.conf file. (I hope the problem repeats in your machines too)

Comment 1 Sheldon Hearn freebsd_committer

2000-08-07 12:31:11 UTC

Responsible Changed
From-To: freebsd-bugs->des

Revisions 1.181 and 1.182, which introduced this line into etc/rc, 
belong to DES.

Comment 2 des 2000-08-30 10:25:44 UTC

yurtesen@ispro.net.tr writes:
> When I have nis_client_enable="YES" in my /etc/rc.conf file the boot
> process is haning at line
> chown root:wheel /dev/tty[pqrsPQRS]*
> of the /etc/rc file when I comment out this line the machine boots
> correctly. The same happened in 2 different machines I use here.
> Somebody may lock out himself when rebooting the machine or they
> might need to go to system room to press ctrl-c to cancel chown and
> continue booting. After a power failure machines would not boot
> correctly! So this is kinda serious problem I guess... ?

This comes from a combination of:

 a) you have enabled NIS without properly configuring a NIS server, or
    (the connection to) your NIS server is down

 b) you have (improperly) left out local entries for root and wheel in
    your password and group files.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no

Comment 3 yurtesen 2000-08-30 11:48:53 UTC

Well it was because of some chown line in /etc/rc file since rc tries to
run chown before the nis initializes it wasnt able to find the root user
so waiting for a timeout I guess. Putting the line after the lines which
initializes NIS solved the problem.

Evren

On 30 Aug 2000, Dag-Erling Smorgrav wrote:

> yurtesen@ispro.net.tr writes:
> > When I have nis_client_enable="YES" in my /etc/rc.conf file the boot
> > process is haning at line
> > chown root:wheel /dev/tty[pqrsPQRS]*
> > of the /etc/rc file when I comment out this line the machine boots
> > correctly. The same happened in 2 different machines I use here.
> > Somebody may lock out himself when rebooting the machine or they
> > might need to go to system room to press ctrl-c to cancel chown and
> > continue booting. After a power failure machines would not boot
> > correctly! So this is kinda serious problem I guess... ?
> 
> This comes from a combination of:
> 
>  a) you have enabled NIS without properly configuring a NIS server, or
>     (the connection to) your NIS server is down
> 
>  b) you have (improperly) left out local entries for root and wheel in
>     your password and group files.
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@flood.ping.uio.no
>

Comment 4 des 2000-08-30 14:04:48 UTC

Evren Yurtesen <yurtesen@ispro.net.tr> writes:
> Well it was because of some chown line in /etc/rc file since rc tries to
> run chown before the nis initializes it wasnt able to find the root user
> so waiting for a timeout I guess. Putting the line after the lines which
> initializes NIS solved the problem.

No. The problem is that you do not have a local root user or wheel
group, which is a configuration error.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no

Comment 5 Dag-Erling Smørgrav freebsd_committer

2000-08-30 14:12:05 UTC

State Changed
From-To: open->closed

Configuration error.