[sf-lug] Enabling bootlogd

Arnold sait8so at gmail.com
Fri Dec 7 13:38:30 PST 2007


Hello,

Been looking to get the bootlog working and I'd appreciate any help.
The OS is an Etch Netinstall with a minimal XFCE which I use to learn
the CL and venture into new territory. (My main OS is Etch/KDE.)

I edited the /etc/default/bootlogd file to "BOOTLOGD_ENABLE=Yes" but
that didn't work. Next, I found a recent Debian forum thread where
someone posted this CL suggestion for the same problem: "ln -s
/etc/init.d/bootlogd /etc/rcS.d/S00bootlogd". With the new
"S00bootlogd" file in the /etc/rcS.d directory, I rebooted and the
word "failed" scrolled by in red (4th line in log below).

Before doing that command, I had an empty "boot" file in the /var/log/
directory. I've now got the files "boot" "boot.0" and "boot.1.gz".
This is what's in the "boot" file:

Thu Dec 6 04:32:06 2007: Starting the hotplug events dispatcher: udevd.
Thu Dec 6 04:32:06 2007: Synthesizing the initial hotplug events...done.
Thu Dec 6 04:32:06 2007: Waiting for /dev to be fully populated...done.
Thu Dec 6 04:32:06 2007: Starting boot logger: bootlogd ^[[31mfailed!^[[39;49m
Thu Dec 6 04:32:06 2007: Activating swap...done.
Thu Dec 6 04:32:06 2007: Checking root file system...fsck 1.40-WIP (14-Nov-2006)
Thu Dec 6 04:32:06 2007: DebianNet: Superblock last write time is in
the future. FIXED.
Thu Dec 6 04:32:06 2007: DebianNet: clean, 39412/688128 files,
215147/1375557 blocks
Thu Dec 6 04:32:06 2007: done.
Thu Dec 6 04:32:06 2007: Setting the system clock..
Thu Dec 6 12:32:07 2007: Cleaning up ifupdown....
Thu Dec 6 12:32:07 2007: Loading kernel modules...done.
Thu Dec 6 12:32:07 2007: Loading device-mapper support.
Thu Dec 6 12:32:07 2007: Checking file systems...fsck 1.40-WIP (14-Nov-2006)
Thu Dec 6 12:32:07 2007: done.
Thu Dec 6 12:32:07 2007: Setting kernel variables...done.
Thu Dec 6 12:32:07 2007: Mounting local filesystems...done.
Thu Dec 6 12:32:07 2007: Activating swapfile swap...done.
Thu Dec 6 12:32:07 2007: Setting up networking....
Thu Dec 6 12:32:07 2007: Configuring network interfaces...done.
Thu Dec 6 12:32:07 2007: Setting console screen modes and fonts.
Thu Dec 6 12:32:07 2007: ^[]R^[[9;30]^[[14;30]Setting up ALSA...done.
Thu Dec 6 12:32:08 2007: INIT: Entering runlevel: 2
Thu Dec 6 12:32:08 2007: Starting system log daemon: syslogd.
Thu Dec 6 12:32:08 2007: Starting kernel log daemon: klogd.
Thu Dec 6 12:32:09 2007: Starting Advanced Configuration and Power
Interface daemon: acpid.
Thu Dec 6 12:32:09 2007: Starting system message bus: dbus.
Thu Dec 6 12:32:09 2007: Starting Hardware abstraction layer: hald.
Thu Dec 6 12:32:10 2007: ^[[33m*^[[39;49m Not starting internet
superserver: no services enabled. Thu Dec 6 12:32:10 2007: Starting
periodic command scheduler: crond.
Thu Dec 6 12:32:10 2007:

Dunno if this is the problem but there's a shell script in
/etc/init.d/ labeled "stop-bootlogd" - seems its part of a history of
bootlog problems (daemon loading order?) in Debian and Ubuntu. Before
doing any more edits, I wanted to ask you guys about it. I'm looking
to understand where the conflict is and which files are involved.

Thanks,

Arnold




More information about the sf-lug mailing list