Ubuntu
rsyslog package

  1. Bug #1401984
  2. Comment #1

Comment 1 for bug 1401984

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

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.