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

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Feb 25 08:12:26 UTC 2019


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

            Bug ID: 236017
           Summary: security/py-fail2ban: won't change PID-file locate
                    even  'fail2ban_pidfile' assigned.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: epopen at gmail.com
                CC: theis at gmx.at
                CC: theis at gmx.at
             Flags: maintainer-feedback?(theis at gmx.at)

Hi

Because directory '/var' mount by tmpfs, and can't create fail2ban default
pid/sock file directory '/var/run/fail2ban'.
So plan modify these to '/var/run'.

File '/usr/local/etc/rc.conf.d/fail2ban' added and one line only like below
'fail2ban_pidfile="/var/run/fail2ban.pid"'
(Without 'fail2ban_enable="YES"', because fail2ban start very slowly in boot
time, so start it after boot completed.)

But won't affect, still '/var/run/fail2ban/fail2ban.pid'.
(Even 'fail2ban_enable="YES"' added same)

Tried to trace by 'sh -x /usr/local/etc/rc.d/fail2ban' and got result below.
   + fail2ban_pidfile=/var/run/fail2ban.pid
Look like '/usr/local/etc/rc.conf.d/fail2ban' affect.

How-To-Repeat:
run rc script '/usr/local/etc/rc.d/fail2ban'

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


More information about the freebsd-ports-bugs mailing list