Bug #2814
syslog-ng logrotate file assumes systemd
0%
Description
The included /etc/logrotate.d/syslog-ng file for syslog-ng (3.27.1-1.0) assumes that the system is running systemd. Any restarts after subsequent logrotation will
therefore fail, and the main system logging will cease.
This would probably be better handled with a post-install hook if a separate .nonsystemd package is not create which for instance would look like the following:
size 50000k
/var/log/messages.log /var/log/auth.log /var/log/mail.log /var/log/kernel.log /var/log/errors.log /var/log/daemon.log /var/log/user.log /var/log/syslog.log /var/log/acpid.log /var/log/crond.log /var/log/lpr.log /var/log/uucp.log /var/log/news.log /var/log/ppp.log /var/log/debug.log {
missingok
sharedscripts
postrotate
rc-service syslog-ng restart 2>/dev/null || true
endscript
}
History
Updated by Drag0nFly about 2 years ago
Should have written "which for instance looks like the following for OpenRC"
Updated by Zuss 3 months ago
- Status changed from unconfirmed to not-a-bug
Syslog-ng no longer assumes you are using SystemD
Current Syslog-ng v3.36 logrotate file:
$ cat /etc/logrotate.d/syslog-ng
/var/log/messages.log /var/log/auth.log /var/log/mail.log /var/log/kernel.log /var/log/errors.log /var/log/daemon.log /var/log/user.log /var/log/iptables.log /var/log/everything.log /var/log/syslog.log /var/log/acpid.log /var/log/crond.log /var/log/lpr.log /var/log/uucp.log /var/log/news.log /var/log/ppp.log /var/log/debug.log {
missingok
sharedscripts
postrotate
/bin/kill -HUP $(cat /run/syslog-ng.pid 2>/dev/null) 2>/dev/null || true
endscript
}