Having journald in place, rsyslog is no longer strictly necessary, so I
would suggest to stop assuming that rsyslog will be in installed.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.

  logrotate config uses syslog group

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Bionic:
Status in logrotate source package in Cosmic:

Bug description:
  The default logrotate config uses the "syslog" group.

  > # use the syslog group by default, since this is the owning group
  > # of /var/log/syslog.
  > su root syslog

  This is not correct anymore since 16.04, because:

  1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets 
installed via rsyslog
  2. The owning group is actually "adm".

  This results in logrotate terminating with the following error during
  cron.daily run:

  run-parts -v /etc/cron.daily
  run-parts: executing /etc/cron.daily/logrotate
  error: /etc/logrotate.conf:7 unknown group 'syslog'

  And can be fixed by changing syslog to adm group.

  This is not present when rsyslog is installed, but only because that package 
creates the syslog group. This is a common bug in lighter environments, like 
Docker, where syslog-ng is a common choice instead of rsyslog, like in this 

To manage notifications about this bug go to:

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

Reply via email to