I'm using fail2ban 0.8.14 on CentOS5. The pyinotify backend is selected. It seems like globs are only used at startup time, which means that my Java webserver logs that are named with embedded dates only work for one day.
Example: logpath = /usr/local/jetty/logs/*request.log Fails to find tomorrow's log when it is generated by the webserver: /usr/local/jetty/logs/2015_03_06.request.log It seems to be fairly common for Jetty and JBoss to manage their own log rotation, and they both include the date in the filename by default. Has this issue been fixed in a later release? Can I use a different notify backend to work around it? Is it possible to send the fail2ban server a "HUP" signal or "re-read logpaths" command periodically via cron job? ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
