Have you tried looking through /var/log/messages?
There are various logging mechanisms used by various startup items.
Perhaps you can narrow the gamut a little and tell us what is failing?
Cheers
Todd
Systems Administrator
---------------------------------------------
Soho VFX - Visual Effects Studio
99 Atlantic Avenue, Suite 303
Toronto, Ontario, M6K 3J8
(416) 516-7863
http://www.sohovfx.com
---------------------------------------------
On Dec 10, 2007, at 3:45 PM, Linda Walsh wrote:
Is there any easy way to save the boot-time output after the kernel
has booted and init has started running '/etc/rc.d/boot'?
Specifically, on virtually every system, at times, messages just wiz
by on a bootup (especially after upgrades). Problem is that these
init-boot-script error messages are not saved anywhere. They are
echoed to the console with error messages occasionally spitting out
interspersed with other startup messages, but its hard to track
everything down when the messages flit by so fast.
Sometimes I can scroll back on the console and see some of them,
but the scrollback buffer often doesn't go all the way back to
where the dmesg output (also in /var/log/boot.log) stops. Also,
simply scrolling back doesn't help get it into a file -- since if
you want to use the console, or when other messages get output to
the console the boot-startup messages get scrolled off the top of
the text buffer.
It'd be nice if "boot" could log all console output to a temp file
that would be copied into /var/log like boot.msg, on each system
startup. I'd expect startup logging to stop as soon as login is
spawned to allow user login -- hopefully steering around any
user-privacy issues.
Is this easily doable in the current setup?
Thanks,
Linda
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
