Date: Wed, 27 Feb 2019 10:41:45 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 236017] security/py-fail2ban: won't change PID-file locate even 'fail2ban_pidfile' assigned. Message-ID: <bug-236017-7788-MpOZoRRN5u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236017-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-236017-7788@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=3D236017 --- Comment #3 from theis@gmx.at --- I just tried: Stop fail2ban Change the paths for pidfile and socket in fail2ban.conf Add fail2ban_pidfile=3D... in /etc/rc.conf (I'm still using the old scheme) Start fail2ban was successful, both pid- and sock-file were in /var/run I don't know if I understand you correctly. Just in case there are misunderstandings: You have to change both, fail2ban.conf and /etc/rc.conf = (or wherever you are configuring the services) because the first one tells fail= 2ban where to write the pidfile and the latter one tells the service where to fi= nd it. From the error message in your post it looks like the service is still looking at the old place and of course will not find the pid-file there. --=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-236017-7788-MpOZoRRN5u>