py-fail2ban turned silent after syslogd rollout (r335059, stable/11)
Michael Grimm
trashcan at ellael.org
Fri Jun 22 17:14:58 UTC 2018
On 22. Jun 2018, at 17:59, Marek Zarychta <zarychtam at plan-b.pwste.edu.pl> wrote:
> Could you please give any advice or workaround for this issue?
I switched to a workaround for the time being which you might use as well in a similar way:
#) configure fail2ban to use /var/log/faillog
#) run something like that in the background:
nohup tail -q -F /var/log/fail2ban.log | logger -t fail2ban.filter -p daemon.notice &
#) to let this workaround survive a reboot you need to use a script fired up from /etc/rc.d
Regards,
Michael
More information about the freebsd-ports
mailing list