Your message dated Sat, 12 Sep 2009 00:58:08 +0200
with message-id <[email protected]>
and subject line Re: sysvinit: bootlog does not work
has caused the Debian Bug report #368785,
regarding sysvinit: bootlog does not work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
368785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368785
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit
Version: 2.86.ds1-1
Severity: normal
After booting, /var/log/boot is still empty. I don't know if there's
an error message: the messages are output too quickly on the screen.
There's nothing in the various log files (and dmesg output) anyway,
and bootlog is stopped without any error:
Stopping Bootlog daemon: bootlogd.
I have:
crw------- 1 root root 5, 1 2006-05-24 15:00:23 /dev/console
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Versions of packages sysvinit depends on:
ii coreutils 5.2.1-2 The GNU core utilities
ii initscripts 2.86.ds1-1 Standard scripts needed for bootin
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii sysv-rc 2.86.ds1-1 Standard boot mechanism using syml
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2009-09-10 23:44:44 +0200, Petter Reinholdtsen wrote:
> Is bootlogd still not working for you? It works for me when I test
> it, and there is not enought information in your bug report to have
> any idea how to replicate the problem you reported. Can you provide
> more information?
The machine no longer exists and I don't have any problem on my
other machines. So, I'm closing the bug.
> What is the content of your /etc/default/bootlogd ?
I don't remember. But note that in my bug report I said that I got:
Stopping Bootlog daemon: bootlogd.
This means that bootlog was enabled, because the $BOOTLOGD_ENABLE
test occurs before the message is printed.
--
Vincent Lefèvre <[email protected]> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
--- End Message ---
