==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
http://bugs.contribs.org/show_bug.cgi?id=8708
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
Daniel B. <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Daniel B. <[email protected]> ---
I've just pushed new smeserver-fail2ban on fws' repo. I don't have an
explanation for fail2ban not being restarted during logrotate as I can't
reproduce it. Anyway, I've changed the way log rotation is handled. Instead of
restarting the whole fail2ban daemon during logrotate event, I start by
dynamically remove logs which will be rotated (using fail2ban-client set
http-scan dellogpath /var/log/httpd/error_log for example), then logrotate
occures, then, I add back the logs to be monitored. This is also much more
efficient as you don't loose all the blacklisted hosts during logrotate.
Marking FIXED in smeserver-fail2ban-0.1.9-1.sme (and
smeserver-fail2ban-0.1.10-1.sme for SME9)
%changelog
* Tue Jan 27 2015 Daniel Berteaud <[email protected]> - 0.1.9-1.sme
- Suspend log monitoring during logrotate [SME: 8708]
Please, test it and confirm if it fixes your issue
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
