Date: Fri, 22 Jun 2018 21:26:36 +0200 From: Michael Grimm <trashcan@ellael.org> To: Ed Schouten <ed@nuxi.nl> Cc: "ed@FreeBSD.org" <ed@freebsd.org>, theis@gmx.at, Gleb Smirnoff <glebius@freebsd.org>, 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: <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> In-Reply-To: <CABh_MKkdObTmbNXnKrudyHjkd8s3aukUUC=Vee%2BRShJepWpwNg@mail.gmail.com> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> <CABh_MKkdObTmbNXnKrudyHjkd8s3aukUUC=Vee%2BRShJepWpwNg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22. Jun 2018, at 21:11, Ed Schouten <ed@nuxi.nl> 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 this patch a try? Thanks! Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd with the re-compiled one, and: Thank you! Your patch is working w.r.t. fail2ban logging to SYSLOG. Perfect! Thank you very much for this fast fix, and regards, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?851C065F-0E02-425C-B4AF-8FCE0E405F8E>