Re: Bug#1396: System Hangs!
Bill Mitchell writes:
>Raul Miller <moth@magenta.com>
>> Dale Scheetz asks:
>> Well, absolutely nothing appears in the log after the last boot
>> message. BTW the major things that appear on the console but not in
>> the messages log is the output from the boot script and
>> run-parts. What do I do to get these messages into a file
>> somewhere?
>>
>> si::sysinit:/etc/init.d/boot >>/var/log/boot
>>
>> [I think that all log files in /var/log/ are automatically
>> rotated?]
If you look in /etc/cron.*/* you'll find various calls to savelog.
This is what does the rotation.
>I just rendered my system unbootable by trying this.
>(rummages for a disaster disk)
>
>The redirection apparently fails because the root filesystem is mounted
>readonly, and thish screws up the rest of the system startup.
Another failure mode is when /var is on a separate partition from /,
in which case it won't have been mounted yet. The only way to do it
would be for init to catch the output from its commands and send it to
a log file later when it magically found out that the log file had
become writable. This won't solve problems that occur before the call
to mount, and has got to be more effort than it's worth...
One could redirect the output to a printer, perhaps.
>If this can be made to work, I was thinking that "| tail -a
>/var/log/boot" might be better than the simple redirection.
richard@muskogee:~/debian$ tail -a /var/log/boot
tail: illegal option -- a
Try `tail --help' for more information.
richard@muskogee:~/debian$
What does -a do on yours?
--
Richard Kettlewell richard@uk.geeks.org http://www.elmail.co.uk/staff/richard/
Reply to: