Control: affects -1 rsyslog Revisiting this bugreport...
I think the original issue (message #5) from mbraun, that snmptrapd.log is not being rotated, should be fixed nowadays or was a misconfiguration. The followup issues (messages #10 and #22) from sixerjman and Harald seem to be a duplicate of #720096. Reading https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720096#145, sending two SIGHUP signals in a very short time interval (one in postrotate of /var/log/syslog and one in postrotate of the other rsyslog logs) might be a cause. The option 'delaycompress' might make timing difference. Maybe adding a timeout for rsyslog to come back alive after a SIGHUP in /usr/lib/rsyslog/rsyslog-rotate could solve this issue? Best regards, Christian Göttsche
