[Bug 236017] security/py-fail2ban: won't change PID-file locate even 'fail2ban_pidfile' assigned.

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236017

--- Comment #3 from theis at gmx.at ---
I just tried:
Stop fail2ban
Change the paths for pidfile and socket in fail2ban.conf
Add fail2ban_pidfile=... 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 fail2ban
where to write the pidfile and the latter one tells the service where to find
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.