Date: Fri, 22 Jun 2018 20:13:59 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> Cc: freebsd-stable@freebsd.org, ed@freebsd.org Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622181359.GQ4028@home.opsec.eu> In-Reply-To: <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > >> 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 > > > > > > I have rolled back to r334835. The issue has gone. Should a PR be > created about this regression ? Yes, please. > BTW a few decent syslog daemons are available in /usr/ports/sysutils. -- pi@opsec.eu +49 171 3101372 2 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180622181359.GQ4028>