Hello :-)
Subject: bootlogd 2.86.02 boot script link change to capture more boot
messages
Regards the workaround for this bug ('cos it ain't going away any time
soon!).
After installing bootlogd 2.86.02 from the package Sergei attached to
this bug report (thanks Sergei) ...
bootlogd is started by /etc/rcS.d/S12bootlogd which is a symbolic link
to /etc/init.d/bootlogd. S12bootlogd is not the first S* entry in
/etc/rcS.d/ so bootlogd does not catch output from earlier S* entries.
On my system (ubuntu 8.04.2), boot messages from the following were not
logged:
S01mountkernfs.sh
S01readahead
S02hostname.sh
S06keyboard-setup
S07linux-restricted-modules-common
S08hwclockfirst.sh
S08loopback
S10udev
S11hwclock.sh
S11mountdevsubfs.sh
Boot messages from the above can be logged by making bootlogd start
before them. The following commands, run by root, will do the trick.
cd /etc/rcS.d
rm S12bootlogd
ln -s ../init.d/bootlogd S01bootlogd
I expected this change to cause some breakage; perhaps bootlogd depended
on something set by the earlier boot scripts; why would the package
designers not start it right at the beginning of the boot process so it
could capture all the boot messages?
But it tested OK. YYMV. In case it does cause serious breakage it is
prudent to ensure you can boot something else (ubuntu installation CD,
Knoppix etc) and remove /etc/rcS.d/S01bootlogd if needs must.
Best
Charles
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
