Description of problem: could you add a logrotate cfg file for /var/log/fail2ban.log Version-Release number of selected component (if applicable): 0.8.0-4.fc6 and devel Additional Info: Just want to put this here so I/we don't forget this RFE... I'm actually not sure what the "proper" way to notify the new 0.8 daemon to start logging to a new log file once logrotate has moved the current one away... when I get a chance I'll take a look at it, unless someone else has done the work already... I'd like something similar to yum's logrotate by default (size based vs time based) but whatever works. thanks.
Have you tried creating a file in /etc/logrotate.d called fail2ban and containing this: /var/log/fail2ban.log { missingok notifempty size 30k create 0600 root root } If you can verify that that works, I'm sure Axel could add it to the rpm at some point.
i should have mentioned i did try that config from yum logrotate, but in my minimal testing it did _not_ work... fail2ban just kept logging to the old log file: /var/log/fail2ban.log.1. i think the checked in fix in cvs won't work, but I might be wrong in my quick testing prior...
i need to add a reload and this works for me: --- fail2ban-logrotate.orig 2007-05-23 15:16:34.000000000 -0400 +++ fail2ban-logrotate 2007-05-23 15:17:09.000000000 -0400 @@ -3,4 +3,7 @@ notifempty size 30k create 0600 root root + postrotate + /usr/bin/fail2ban-client reload 2> /dev/null || true + endscript }