touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #42371
[Bug 1401984] [NEW] non persistent logging after cleaning log files on disk
Public bug reported:
Using current vivid with systemd init, I've cleaned the log on disk
(*.log syslog dmesg) and rebooted my test box, since then it stopped
logging to syslog.
journalctl has the log from the current boot but not from previous ones
the behaviour there is a bit confusing, I first though that I would get
a fresh syslog on next boot and not an auto conversion to use journald,
then the journal should keep record from previous boots as well...
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1401984
Title:
non persistent logging after cleaning log files on disk
Status in systemd package in Ubuntu:
New
Bug description:
Using current vivid with systemd init, I've cleaned the log on disk
(*.log syslog dmesg) and rebooted my test box, since then it stopped
logging to syslog.
journalctl has the log from the current boot but not from previous
ones
the behaviour there is a bit confusing, I first though that I would
get a fresh syslog on next boot and not an auto conversion to use
journald, then the journal should keep record from previous boots as
well...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401984/+subscriptions
Follow ups
References