Comment 31 for bug 940030

I've tested this on Ubuntu 16.04 with rsyslog version 8.16.0-1ubuntu3 on an install with systemd and I also tested it on the Bionic Beaver, which will become Ubuntu 18.04, with rsyslog version 8.16.0-1ubuntu10 on an install also with systemd and was unable to recreate the bug my test case on both releases follows.

1) Run 'sudo logrotate --force /etc/logrotate.conf /etc/logrotate.d/rsyslog'
2) Observe /var/log/syslog with recent timestamp
3) Run 'sudo service cups restart'
4) 'cat /var/log/syslog'
5) Observe messages regarding the restart of cups in the log file

In the event that anyone is still experiencing this issue please include detailed information about the version of rsyslog you have installed, whether or not using are using systemd, and the release of Ubuntu which you are running.