py-fail2ban turned silent after syslogd rollout (r335059, stable/11)

[Kurt Jaeger]

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 at opsec.eu            +49 171 3101372                    2 years to go !