tags 439962 + etch
thanks
I believe that the issue is the one fixed in 0.7.8-1 (without a
corresponding bug ever recorded) and which
propagated upstream and was released with 0.7.9
iirc change was quite substantial to propagate into 0.7.5 as a security
update (the one I am loong planning to do, heh heh).
on the other hand it could be related to 410077, for that we had to know
if there was external command (like mail) stalled within fail2ban's
call.
> Undoubtedly, cron.daily or logrotate could use timeouts. Until they
> do, this is a critical bug in fail2ban because it breaks unrelated
> software.
is there a facility in logrotate's config file to specify timeout
duration? please pardon my ignorance if such
--
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]
