From owner-freebsd-python@FreeBSD.ORG Mon Oct 28 07:10:02 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0996BC01 for ; Mon, 28 Oct 2013 07:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D124626DE for ; Mon, 28 Oct 2013 07:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9S7A15b086178 for ; Mon, 28 Oct 2013 07:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9S7A1rw086173; Mon, 28 Oct 2013 07:10:01 GMT (envelope-from gnats) Date: Mon, 28 Oct 2013 07:10:01 GMT Message-Id: <201310280710.r9S7A1rw086173@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Christoph Theis Subject: Re: ports/167530: [patch] security/py-fail2ban will never ever start with the given rc.d script X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Christoph Theis List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 07:10:02 -0000 The following reply was made to PR ports/167530; it has been noted by GNATS. From: Christoph Theis To: koobs@FreeBSD.org, bug-followup@FreeBSD.org Cc: julien@tayon.net Subject: Re: ports/167530: [patch] security/py-fail2ban will never ever start with the given rc.d script Date: Mon, 28 Oct 2013 08:00:17 +0100 Hi all! Julien and me continued the discussion off-the-list and found out that it was a mistake in the way fail2ban was installed. A proper installation fixed the issue. So we can close this bug report. Christoph