From theis@gmx.at  Thu May  3 06:40:42 2012
Return-Path: <theis@gmx.at>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E3AFC106566B
	for <bug-followup@FreeBSD.org>; Thu,  3 May 2012 06:40:42 +0000 (UTC)
	(envelope-from theis@gmx.at)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23])
	by mx1.freebsd.org (Postfix) with SMTP id 4DB078FC12
	for <bug-followup@FreeBSD.org>; Thu,  3 May 2012 06:40:42 +0000 (UTC)
Received: (qmail invoked by alias); 03 May 2012 06:40:40 -0000
Received: from unknown (EHLO [192.168.0.100]) [188.21.181.54]
  by mail.gmx.net (mp035) with SMTP; 03 May 2012 08:40:40 +0200
Message-Id: <4FA22868.7090009@gmx.at>
Date: Thu, 03 May 2012 08:40:40 +0200
From: Christoph Theis <theis@gmx.at>
To: julien tayon <julien@tayon.net>
Cc: bug-followup@FreeBSD.org
In-Reply-To: <CAFpLVkwVJ9OejJ8kn0FGRRjKLXBytqtqOgfHjtbqa-k40WgAwg@mail.gmail.com>
Subject: Re: fail2ban port bug issue
References: <CAFpLVkwVJ9OejJ8kn0FGRRjKLXBytqtqOgfHjtbqa-k40WgAwg@mail.gmail.com>

>Number:         167553
>Category:       ports
>Synopsis:       Re: fail2ban port bug issue
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 03 06:50:10 UTC 2012
>Closed-Date:    Thu May 03 07:49:46 UTC 2012
>Last-Modified:  Thu May 03 07:49:46 UTC 2012
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Hello!
 
 Am 02.05.2012 20:21, schrieb julien tayon:
 > I just installed freebsd, and stumbled on a bug in the ports of
 > /usr/ports/security/py-fail2ban
 >
 > I filled a bug here http://www.freebsd.org/cgi/query-pr.cgi?pr=167530
 > the correction on the /etc/usr/local/etc/rc.d startup script is
 > included
 >
 >
 > But on irc everybody told me to contact you instead, I find this pretty weired.
 
 Indeed, that is strange. I know the script is working ,)
 
 If I read your suggested patch correctly you will start the server 
 (fail2ban-server) instead of the client. According to the manual (I'm no 
 expert on fail2ban, just maintaining the port) the server doesn't know 
 anything of the configuration. The client will read configuration and 
 send appropriate commands to the server. So unless there is a client 
 around the server would do nothing.
 
 Starting the client as "fail2ban-client start" the client will first 
 start the server, wait until the server is running and then proceed 
 configuring the server. If the script hangs and doesn't return the the 
 command prompt either the server did not start and the client still 
 waits (I don't know if there is a timeout) or there is a problem reading 
 configuration.
 
 The command is started by the python interpreter. "ps aux" may show only 
 the name of the interpreter, I had luck with "ps waux | grep fail"
 
 There shall be a unix socket /var/run/fail2ban/fail2ban.socket if the 
 server is running. You may check for that one, too.
 
 Else you may start the client with verbosity set (-v).
 
 
 Best regards
 
 Christoph
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Thu May 3 07:49:13 UTC 2012 
State-Changed-Why:  
Misfiled followup to ports/167530; content migrated. 


Responsible-Changed-From-To: gnats-admin->freebsd-ports-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu May 3 07:49:13 UTC 2012 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=167553 
>Unformatted:
