This is caused by gamin bug #926862. A correct fix to gamin is available and should be applied to that package in preference to changing fail2ban to use filesystem polling.
As far as I can tell, this is a security issue since fail2ban (and presumably other monitoring daemons) will silently ignore intrusions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954453 Title: fail2ban in precise defaults to gamin, does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/954453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs