lkml.org 
[lkml]   [1996]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Reboot - results in unable to detect run level
Date
In article <9606191915.AA14922@athos.mas.vcu.edu>,
Marko Siladin <msiladin@athos.mas.vcu.edu> wrote:
>In the last couple of weeks I have run into problems with
>rebooting the machine. Sometimes the result of typing
>reboot at the root prompt results in a message that the
>root level cannot be determined and that a hard reset
>will be performed instead. First I thought that the reason
>might me a faulty sysvinit so I upgraded to the latest version
>2.63 - (from 2.57b - whaterver came with Slakware 3.0) but
>the it seems like that did not solve the problem since it
>appeard again today. Any clues where I should look? There
>were no suspicious messges in /var/log/*.
>I'm running all the stuff from Documentation/Changes.

This does not belong in linux.dev.kernel, but oh well. Something is trashing
your /var/run/utmp file, thereby removing/overwriting the runlevel entry.
Just use "shutdown" instead of reboot/halt (eg "shutdown -r now").

Mike.
--
Miquel van | Cistron Internet Services -- Alphen aan den Rijn.
Smoorenburg, | mailto:info@cistron.nl http://www.cistron.nl/
miquels@het.net | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.032 / U:0.852 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site