On 09/22/2016 06:22 AM, Grant wrote: > If I enable the recidive filter, fail2ban won't start if the > fail2ban.log file doesn't exist yet. I'm deploying this in an > environment that starts fresh every day. Should I just touch > fail2ban.log before starting fail2ban or is there a more graceful > method for avoiding this issue? > > - Grant
I think this could reasonably be considered a bug in that fail2ban should have created the logfile before the jail code starts to look for it. Alternatively you could log to syslog or the journal and have recidive monitor that. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane [email protected] Boulder, CO 80301 http://www.nwra.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
