?? existence of /etc/rc.conf causes init problem

?? existence of /etc/rc.conf causes init problem

Post by Chen X » Tue, 21 Mar 2000 04:00:00



Hi All,

I was trying to put and old 486 into use. It has 50Mhz motherboard and 50M mem.
The installation went great! The first reboot after install went OK too, the
system comes up normally.

However, after
#cp /etc/defaults/rc.conf /etc/rc.conf
and reboot again, the first part of the booting was OK (highlighted message,
detecting hardware etc.), but it hanged at line
"change root device to wd0s1a" .

After about 5 mins, it said
".: out of file descriptor"

and then dropped me into single user mode. I played around and
found if no /etc/rc.conf exists, the system boots and inits fine.

I don't understand why. Any ideas?  

--

Structural Biology Program                      Tel: (212)263-1596
Skirball Institute of Biomolecular Medicine     Fax: (212)263-8951
New York Uni Medical Center -- 540 First Ave -- New York, NY 10016

 
 
 

?? existence of /etc/rc.conf causes init problem

Post by Richard Tob » Tue, 21 Mar 2000 04:00:00




Quote:>However, after
>#cp /etc/defaults/rc.conf /etc/rc.conf
>and reboot again, the first part of the booting was OK (highlighted message,
>detecting hardware etc.), but it hanged at line
>"change root device to wd0s1a" .

/etc/rc.conf should not be a copy of /etc/defaults/rc.conf, but just
settings of variables that you don't want the defaults for.

/etc/defaults/rc.conf *runs* /etc/rc.conf, so if it's a copy of it
you will have an infinite loop!

-- Richard
--
Spam filter: to mail me from a .com/.net site, put my surname in the headers.

"The Internet is really just a series of bottlenecks joined by high
speed networks." - Sam Wilson

 
 
 

?? existence of /etc/rc.conf causes init problem

Post by Matthew Jenkin » Wed, 22 Mar 2000 04:00:00


The last couple of lines in /etc/defaults/rc.conf load /etc/rc.conf - hense,
if you copy the former to the latter:
    /etc/rc.conf loads:
        /etc/rc.conf, which in turn loads:
            /etc/rc.conf, which in turn loads:
                /etc/rc.conf, which in turn loads:
                    /etc/rc.conf, which in turn loads:
                        /etc/rc.conf, which in turn loads:
                            /etc/rc.conf, which in turn loads:
                                /etc/rc.conf, which in turn loads:
                                    /etc/rc.conf, which in turn loads:
                                        /etc/rc.conf, which in turn loads:
                                            /etc/rc.conf, which in turn
loads:
                                                /etc/rc.conf, which in turn
loads:
                                                    /etc/rc.conf, which in
turn loads:
                                                        /etc/rc.conf, which
in turn loads:
                                                            /etc/rc.conf,
which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

/etc/rc.conf, which in turn loads:

Is your brain out of file descriptors yet?

Matt
--
You can kill the revolutionary
But you can't kill the revolution!


: Hi All,
:
: I was trying to put and old 486 into use. It has 50Mhz motherboard and 50M
mem.
: The installation went great! The first reboot after install went OK too,
the
: system comes up normally.
:
: However, after
: #cp /etc/defaults/rc.conf /etc/rc.conf
: and reboot again, the first part of the booting was OK (highlighted
message,
: detecting hardware etc.), but it hanged at line
: "change root device to wd0s1a" .
:
: After about 5 mins, it said
: ".: out of file descriptor"
:
: and then dropped me into single user mode. I played around and
: found if no /etc/rc.conf exists, the system boots and inits fine.
:
: I don't understand why. Any ideas?
:
: --

: Structural Biology Program                      Tel: (212)263-1596
: Skirball Institute of Biomolecular Medicine     Fax: (212)263-8951
: New York Uni Medical Center -- 540 First Ave -- New York, NY 10016
:

 
 
 

1. /etc/rc: sendmail parms don't match /etc/rc.conf

Or do they?

Here's what is in /etc/rc.conf and should be passed to sendmail
during startup:

Here's what my slightly-modified /etc/rc writes to the console
during boot:

And here's what ps awux|grep sendmail shows when all the /etc/rc*
scripts finish running and I can get logged on:

And I have to start sendmail manually, which is a real PITA.

Any ideas on what's causing this and how to fix it?

Alternatively, any ideas on how to instrument things so I'll
have a better chance of finding the cause?

--
Nature and nature's laws lay hid in night,
God said, "Let Newton be," and all was light.
It did not last; the devil howling "Ho!
Let Einstein be!" restored the status quo.

2. ide_dmaq_intr: stat=40, not expected

3. INIT and restarting /etc/rc.conf...

4. Help on asppp for Solaris 2.6 x86

5. How To Keep Login Refused Out of Messages

6. /etc/rc.net, /etc/host.conf and ps problems

7. Ftp-proxy on 3.0

8. SOLUTIONS TO: /etc/rc.net, /etc/host.conf and 'ps' problems

9. difference between /etc/rc.sysinit and /etc/rc.d/rc.sysinit ?

10. init: cannot execute "/etc/rc.d/rc.S"

11. REQUEST /etc(/rc.d/rc.*) conf. files for SLIP connection

12. Script to create startup scripts in /etc/init.d or /etc/rc?.d