[Pkg-sysvinit-devel] Bug#791907: bootlogd: /var/log/boot is empty with systemd
vincent at vinc17.net
Thu Jul 9 12:16:32 UTC 2015
Justification: renders package unusable
bootlogd is unusable because /var/log/boot is empty; actually it just
(Nothing has been logged yet.)
I have done the following:
1. Install bootlogd.
This is a Debian/unstable machine with the systemd init system,
which was upgraded from Jessie to unstable.
* There are other bug reports about empty /var/log/boot, but they are
old and might come from bug 716948 (on another machine in the past, I
had to uninstall/reinstall bootlogd because it was no longer working
due to this bug), which is not related to the current problem.
* On other machines with sysvinit, bootlogd runs fine.
* Bug 754443 is about whether bootlogd is still useful with systemd.
Well, what can I tell is that the systemd log doesn't seem to be
sufficient (just like syslog wasn't sufficient) because some messages
are not sent to the log system. For instance, this is the case of
/etc/init.d/networking verbose output.
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bootlogd depends on:
ii libc6 2.19-18
ii lsb-base 4.1+Debian13+nmu1
bootlogd recommends no packages.
bootlogd suggests no packages.
-- no debconf information
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
More information about the Pkg-sysvinit-devel