Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jun 2018 20:02:32 +0200
From:      Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
To:        freebsd-stable@freebsd.org
Cc:        ed@freebsd.org
Subject:   Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11)
Message-ID:  <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl>
In-Reply-To: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>
References:  <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63
Content-Type: multipart/mixed; boundary="64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb";
 protected-headers="v1"
From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
To: freebsd-stable@freebsd.org
Cc: ed@freebsd.org
Message-ID: <b4074f85-bf12-b13b-a92f-69e4c3e84435@plan-b.pwste.edu.pl>
Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059,
 stable/11)
References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org>
 <20180622155922.GA61217@plan-b.pwste.edu.pl>
 <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>
In-Reply-To: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>

--64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US



W dniu 2018.06.22 o=C2=A019:14, Michael Grimm pisze:
> On 22. Jun 2018, at 17:59, Marek Zarychta <zarychtam@plan-b.pwste.edu.p=
l> 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 we=
ll 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 fir=
ed up from /etc/rc.d
>
>

I have rolled back to r334835. The issue has gone. Should a PR be
created about this regression ?

BTW a few decent syslog daemons are available in /usr/ports/sysutils.
--=20

Marek Zarychta



--64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb--

--3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlstOb4ACgkQdZ/s//1S
jSx9bwf+P8u3O48VJYCWns1oL0mW9PzpihuBD7KKaspVhv73pEV9V+fFVcwO+YlK
FWtKSK6BLiiZC+6Bl2VpkC/ZBRjnRVGf1rYIY30NQEIaEwYDqnmCBHV/DlFkA1JD
jfbjHWtLpjxx0mKzJoNWbxKrY4pciGmLGFEfYdhB9tTkVlbQfCXthzsHxk4DBKSB
UqENxHTotRu02o4mpPVcMIMx0myRgWvD7youfuHMyUh8eDPvADvysG3xnIG2SweN
JJ8DphyVPrGyE49CfCtUnSIVOtXHNnHoTNlgWBdVoaumwubEM9sMsf+iymReg2FQ
pQBSjM/Asc3G6PEk1mw4kjUaWxDzPQ==
=6dDZ
-----END PGP SIGNATURE-----

--3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b4074f85-bf12-b13b-a92f-69e4c3e84435>