Thanks for the note... if we are on this path here is another one:
the issue should resolve itself (ie fail2ban should start properly)
after 1st of March comes and your logrotate actually rotates the log
files so there is no entries in currently watched by fail2ban with date
of Feb 29.
So just stay cool on Feb 29 ;-)
On Fri, 29 Feb 2008, Christopher Hagar wrote:
> Note: To be explicit, this bug also results in fail2ban not banning
> attacking IPs. Applying fail2ban-leapyear-autopatch.sh above fixes that
> problem also, in addition to the CPU usage. (Debian etch, package
> version: 0.7.5-2etch1)
> Thank you Mr Halchenko for your rapid response!
> See you in four years,
> Chris Hagar
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
