[EMAIL PROTECTED] wrote:
Carlos E. R. scribbled:
I'll make a somewhat educated guess.
The startup scripts can run in parallel, but I think the output is
delayed, and printed to the screen at the end of each script, or earlier
if a timeout ends first. Thus, they appear ordered in the screen.
However, the log logs them in the same order as they are generated,
intercalated.
To do what you want you have to read the documentation of whatever they
use to capture those messages, at a time the filesystem is not fully
mounted (thus stored in memory), and see if it allows dumping in order to
another file. If not, perhaps you can code it.
---
For now, it appears using a filter on "boot.msg" displays most
of the errors I remember. Working on those is a best first step.
those are all there is... :-)
To add: You can force serial startup through the use of the RUN_PARALLEL
flag in /etc/sysconfig/boot, change it from "yes" to "no" and you will
have a more structured boot.msg. IIRC there should also be a way to get a
prompt to start each service during bootup. I wish I could find it right
now, perhaps someone else can fill in the blanks, but that may be your
best bet for seeing exactly what is happening on your system.
---
The options you refer to are used in /etc/init.d/
I don't want "real-time" observation. These things act more like
a watched pot. I.e. "A watched pot never boils"... The linux machines
I'm updating are in another room -- so I am not usually in front of their
shared console console unless I need to be. When I've made many changes on
a machine (packages updated, upgrading packages from previous releases to
newer releases, new kernel..etc) I want to be able to review boot messages
to look for problems or "weirdities"...:-)
This 'sed' line seems to give me what I want for now:
/usr/bin/sed -r 's/<[a-z]+>[^]]+][^]]+]//' </var/log/boot.msg &>
$/tmp/boot-cons.msg
Linda
(off to break something else...:-))
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
