From owner-freebsd-ports@freebsd.org  Fri Jun 22 17:14:57 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA483102160F;
 Fri, 22 Jun 2018 17:14:57 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.41.56])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 61E0777C71;
 Fri, 22 Jun 2018 17:14:57 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d]
 (p200300E97F1B7801DD22E1F206988F0D.dip0.t-ipconnect.de
 [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 41C4tw23G8z29Q;
 Fri, 22 Jun 2018 19:14:48 +0200 (CEST)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net
From: Michael Grimm <trashcan@ellael.org>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059,
 stable/11)
Date: Fri, 22 Jun 2018 19:14:47 +0200
References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org>
 <20180622155922.GA61217@plan-b.pwste.edu.pl>
To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>,
 Mailing List FreeBSD Ports <freebsd-ports@FreeBSD.org>
In-Reply-To: <20180622155922.GA61217@plan-b.pwste.edu.pl>
Message-Id: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org>
X-Mailer: Apple Mail (2.3445.8.2)
X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2018 17:14:58 -0000

On 22. Jun 2018, at 17:59, Marek Zarychta =
<zarychtam@plan-b.pwste.edu.pl> 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 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

Regards,
Michael