On 22. Jun 2018, at 22:28, Ed Schouten wrote:
> 2018-06-22 22:06 GMT+02:00 Michael Grimm :
>> After applying your patch:
>>Jun 22 21:22:01 HOSTNAME [31033]: NOTICE [JAILNAME]
>> Unban x.x.x.x
>>
>> Watch: 'fail2ban.actions' -the service- is missing.
>
> That's likely due to the fact
On 22. Jun 2018, at 21:26, Michael Grimm wrote:
> On 22. Jun 2018, at 21:11, Ed Schouten wrote:
>> Michael, Marek, could you please give this patch a try? Thanks!
>
> Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd with the
> re-compiled one, and:
>
> Thank you! Your
On 22. Jun 2018, at 21:11, Ed Schouten wrote:
> Gleb, what are your thoughts on the attached patch? It alters syslogd
> to let the 'legacy' RFC 3164 parser also accept messages without a
> timestamp. The time on the syslogd server will be used instead.
>
> Michael, Marek, could you please give
On 22. Jun 2018, at 17:59, Marek Zarychta 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
Marek Zarychta wrote:
> On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote:
>> Hi,
>>
>> this is 11.2-STABLE (r335532), and I am referring to the recent MFC of
>> syslogd modifications [1].
>>
>> Because I cannot judge whether fail2ban lacks support for the renewed
>> syslogd or
Hi,
this is 11.2-STABLE (r335532), and I am referring to the recent MFC of syslogd
modifications [1].
Because I cannot judge whether fail2ban lacks support for the renewed syslogd
or syslogd has an issue in receiving fail2ban messages I do crosspost this mail
to ports and stable.
I do have
