![](https://seccdn.libravatar.org/avatar/ec00c8c2dad5f30d4803320a0b1e352a.jpg?s=120&d=mm&r=g)
On Wed, Nov 07, 2001 at 11:17:28AM -0800, Jack Reilly wrote:
Nick Battle wrote wrote:
What's in the rc.6 directory (I can't remember where it is, but probably under /etc/rc.d or /etc/init.d)? These are the commands that are executed (in order) as runlevel 6 is entered. Do any of them report problems?
/etc/init.d/rc6.d contains only: lrwxrwxrwx 1 root root 9 Mar 13 2001 S20reboot -> ../reboot
I thought surely that was the problem ...only one command to execute. But then I found in the /etc/init.d README:
6 This level is used for rebooting the system. The only valid service for this level is the script reboot, which is linked into /etc/init.d/rc6.d/. The script reboot executes /etc/init.d/halt.local. Specials system issues for halt or reboot should be added there.
I could not find any clue in halt.local, but then I don't do too well reading scripts.
By default there won't be anything in halt.local, just a preamble and a "." of the system configuration file. It is meant for you to put anything special you want to happen when shutting down the system.
Rooting thru a lot of the scripts I am still unable to find the two lines I get before things freeze:
Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level
If I could find the echo commands that produce these two lines I would think that could show the problem.
I dont think that would help. The first is a standard message when run-level 6 is reached, probably issued by /sbin/halt. The second is from init, but you shouldn't normally get it.
The directories /etc/init.d and /etc/rc.d appear to be identical. Is that normal? The identical READMEs that they have, show /init.d as the subject.
/etc/rc.d is a symbolic link to /etc/init.d, so whether you cd /etc/rc.d or cd /etc/init.d You end up in the same place, so don't worry about that. It is for historical compatibility. What you should have in /etc/rc.d/rc.6 is: S20reboot -> ../reboot If you look at ../reboot you will see it itself is a symbolic link to a local file called "halt". This "halt" determines if it has been called by the name "reboot" or the name "halt", in order to decide what action to take. In the case of "halt" it will eventually call /sbin/halt, which is what actually causes the system to "halt". Simple huh ? Mmm..I just tried to find the original source of this thread, but I cannot see it. What was the problem, you cannot reboot ? -- Regards Cliff