[VERIFICATION XENIAL #1]
It has been brought to my attention the following by a Ubuntu user:
"My team confirms that the package which is in -proposed solves our issue."
This user was having issue doing rsyslog logrotation inside a container
which has SYS_PTRACE turned off. Using the systemctl approach fixed
their problem.
[VERIFICATION XENIAL #2]
* On a systemd machine:
$ bash -xv /usr/lib/rsyslog/rsyslog-rotate
#!/bin/sh
if [ -d /run/systemd/system ]; then
systemctl kill -s HUP rsyslog.service
else
invoke-rc.d rsyslog rotate > /dev/null
fi
+ '[' -d /run/systemd/system ']'
+ systemctl kill -s HUP rsyslog.service
* /etc/logrotate.d/rsyslog remains exactly the same minus the fact that
it now calls this 'rsyslog-rotate' helper to take action depending of
systemd or upstart.
* rsyslog rotation works as expected.
This was all tested with rsyslog version: 8.16.0-1ubuntu3.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821582
Title:
Don't rely on SysV init script in logrotate config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1821582/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
