Would it be acceptable resolution for you: * I will add to README.Debian something like
if you use an alternative logtarget (e.g. SYSLOG) thus not using /var/log/fail2ban.log you should divert logrotate configuration into disabled state, i.e. sudo dpkg-divert --rename --divert /etc/logrotate.d/fail2ban.disabled /etc/logrotate.d/fail2ban ? On Tue, 28 Jun 2011, Kenyon Ralph wrote: > Package: fail2ban > Version: 0.8.4-3 > Severity: normal > The fix for http://bugs.debian.org/537773 causes a problem if user has > configured a logtarget other than /var/log/fail2ban.log in > /etc/fail2ban/fail2ban.conf. As you can see below, I have logtarget > set to SYSLOG. So when logrotate runs for fail2ban with > /etc/logrotate.d/fail2ban, the logtarget is set to a file, which I do > not want. > I'm not sure what the best fix for this is. > Personally, I will just remove /etc/logrotate.d/fail2ban, since > nothing needs to happen--my syslog rotation is already taken care of > by /etc/logrotate.d/rsyslog. -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
