Actually, this is not a systemd behavior but seems to be a syslog one. 1. rm /var/log/syslog 2. reboot -> no log (under systemd or upstart) 3. touch /var/log/syslog 4. chmod syslog:adm /var/log/syslog 5. reboot -> logs availables
The cause is that /var/log is 755 and root:syslog (I wonder why it's in syslog group as it's not 775?), and so can't recreate the file. If I chmod syslog, indeed, /var/log/syslog is created, but with other rights, being syslog:syslog instead of syslog:adm. So, it worths more discussion (retargetting to syslog), pinging Martin on this. ** Package changed: systemd (Ubuntu) => rsyslog (Ubuntu) -- 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 -- 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
