Date: Sat, 20 May 2017 14:44:31 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219419] security/py-fail2ban Message-ID: <bug-219419-13-dZKTqYP7Fd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219419-13@https.bugs.freebsd.org/bugzilla/> References: <bug-219419-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219419 --- Comment #1 from theis@gmx.at --- The reason in using fail2ban-python instead of python or python2.7 is that = you may have multiple python installations on your system and python2.7 may not= be among them. Thus the setup of fail2ban detects the python version used and creates a link to fail2ban-python. Did you check that there is a /usr/local/bin/fail2ban-python (or whatever prefix you were using during installation) on your system and is it in the = PATH of the user running fail2ban? You may hardcode the path to fail2ban-python in that file, but in general o= ne has to take care that installation may be in a different path. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219419-13-dZKTqYP7Fd>