On 23 Jun, BARBELET Philippe wrote:
> Please, don't do this because if you have a wrong boot sequence (or a
> problem in it)
> you won't see it and can be stopped whith no way to resolve your
> problem.
>
Opps, your right.
> Use the command "dmesg | more" to see you boot sequence after booting
> or go in the /var/adm directory. There, you'll find the "messages" file
> which receive most of the system messages. You'll find several log files
> also
> that you can edit.
But I think people want an exact list of the output that is generated
after the kernel is done and the init scripts have started. So this is
not the 'complete' solution.
This is just a stab in the dark. But could something like this be done
in /etc/inittab?
How about this:
[snip]
si::sysinit:/etc/init.d/rcS 2>&1 | tee --append /var/log/rcS.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[snip]
l0:0:wait:/etc/init.d/rc 0 2>&1 | tee --append /var/log/rc0.log
l1:1:wait:/etc/init.d/rc 1 2>&1 | tee --append /var/log/rc1.log
l2:2:wait:/etc/init.d/rc 2 2>&1 | tee --append /var/log/rc2.log
l3:3:wait:/etc/init.d/rc 3 2>&1 | tee --append /var/log/rc3.log
l4:4:wait:/etc/init.d/rc 4 2>&1 | tee --append /var/log/rc4.log
l5:5:wait:/etc/init.d/rc 5 2>&1 | tee --append /var/log/rc5.log
l6:6:wait:/etc/init.d/rc 6 2>&1 | tee --append /var/log/rc6.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I don't know I just thought this. I haven't tried it but maybe someone
that understands the startup scripts better can flame me!
Disclaimer: I don't know if this will work and have not tried it so
don't blame me if it breaks your system. You have been warned!
Brian
--
Mechanical Engineering [EMAIL PROTECTED]
Purdue University http://www.ecn.purdue.edu/~servis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
