Bug#760426: [systemd] Logs gone after moving to systemd
Vedran Furač
vedran.furac at gmail.com
Thu Sep 4 01:07:21 BST 2014
Package: systemd
Severity: important
Few days ago I noticed /var/log/syslog was empty. After some time I
found out that this is due to systemd. However, I wasn't warned that
replacing init system will silently break my logs, nor was this
mentioned in documentation. By documentation I mean:
- Package description (mentions that it replaces sysvinit only)
- README.Debian
- wiki.debian.org (systemd page)
- debconf message
Such a huge change must be announced using bold and uppercase and be
documented properly. Debian usually warns through debconf for far more
trivial things.
Also, explain how to configure systemd to use local rsyslog for logging
instead of journal to "emulate" the known and expected behavior.
Regards,
Vedran
--- System information. ---
Architecture: amd64
Kernel: Linux 3.14-1-amd64
Debian Release: jessie/sid
700 testing ftp.de.debian.org
550 experimental ftp.de.debian.org
500 stable ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=========================================-+-==================
libacl1 (>= 2.2.51-8) | 2.2.52-1.1
libaudit1 (>= 1:2.2.1) | 1:2.3.7-1
libblkid1 (>= 2.17.2) | 2.20.1-5.8
libcap2 (>= 1:2.10) | 1:2.24-4
libcryptsetup4 (>= 2:1.4.3) | 2:1.6.6-1
libdbus-1-3 (>= 1.1.1) | 1.8.6-2
libkmod2 (>= 5~) | 18-1
libpam0g (>= 0.99.7.1) | 1.1.8-3.1
libselinux1 (>= 2.1.9) |
libsystemd-journal0 (= 208-7) |
libudev1 (>= 189) |
libwrap0 (>= 7.6-4~) |
libsystemd-login0 (= 208-7) |
util-linux (>= 2.19.1-2) |
initscripts (>= 2.88dsf-53.2) |
sysv-rc |
udev |
acl |
adduser |
libcap2-bin |
More information about the Pkg-systemd-maintainers
mailing list