I've noticed that you slightly modified the syslog-ng init script. I also
noticed that there is no reload option, which I think most distros implement by
HUPing the daemon. I'm having a problem where the firewall log stays at zero
bytes after being compressed by logrotate, even after trying the delaycompress
option. Since the firewall log starts growing again after a restart of
syslog-ng, I imagine putting in a function (already written on the interwebs)
to HUP syslog-ng via a reload argument might fix it. Then people could put that
in the postrotate section of their logrotate configuration.
Original issue reported on code.google.com by lib...@gmail.com on 24 Jun 2012 at 3:09
Original issue reported on code.google.com by
lib...@gmail.com
on 24 Jun 2012 at 3:09