This bug was fixed in the package rsyslog - 7.4.4-1ubuntu12
---------------
rsyslog (7.4.4-1ubuntu12) vivid; urgency=medium
* Install debian/00rsyslog.conf tmpfiles.d snippet to ensure that the syslog
group can write into /var/log/. (LP: #1401984)
-- Martin Pitt <martin.p...@ubuntu.com> Tue, 16 Dec 2014 14:33:34 +0100
** Changed in: rsyslog (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1401984
Title:
non persistent logging after cleaning log files on disk
Status in rsyslog package in Ubuntu:
Fix Released
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/rsyslog/+bug/1401984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
