Date: Fri, 22 Jun 2018 19:14:47 +0200 From: Michael Grimm <trashcan@ellael.org> To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Mailing List FreeBSD Ports <freebsd-ports@FreeBSD.org> Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> In-Reply-To: <20180622155922.GA61217@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22. Jun 2018, at 17:59, Marek Zarychta = <zarychtam@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8103A181-1C50-4EA5-9851-8092861177D8>