inotify backend had already merged into upstream's master branch post
0.8.6 release but there were no upstream release yet.
There is an issue reported against functionality of this backend: https://github.com/fail2ban/fail2ban/issues/44
and it would be great if you could give it some testing. I have updated
'Features' page to refer to github's issues page which would have more
information
> Switching to pyinotify is apparently on the fail2ban roadmap for 0.9.0
> at http://www.fail2ban.org/wiki/index.php/Features so it's probably not
> worth backporting this feature at this point.
> As such the gamin patch should be a reasonable stopgap measure.
inotify backend had already merged into upstream's master branch post /github. com/fail2ban/ fail2ban/ issues/ 44
0.8.6 release but there were no upstream release yet.
There is an issue reported against functionality of this backend:
https:/
and it would be great if you could give it some testing. I have updated
'Features' page to refer to github's issues page which would have more
information
On Mon, 21 May 2012, alp wrote:
> Some background:
> RedHat ported fail2ban to use pyinotify instead of gamin which seems the /bugzilla. redhat. com/show_ bug.cgi? id=658849 and /bugzilla. redhat. com/show_ bug.cgi? id=551895).
> way forward (https:/
> https:/
> Switching to pyinotify is apparently on the fail2ban roadmap for 0.9.0 www.fail2ban. org/wiki/ index.php/ Features so it's probably not
> at http://
> worth backporting this feature at this point.
> As such the gamin patch should be a reasonable stopgap measure.
> ** Bug watch added: Red Hat Bugzilla #658849 /bugzilla. redhat. com/show_ bug.cgi? id=658849
> https:/
> ** Bug watch added: Red Hat Bugzilla #551895 /bugzilla. redhat. com/show_ bug.cgi? id=551895 www.linkedin. com/in/ yarik
> https:/
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://