https://bugzilla.novell.com/show_bug.cgi?id=790557
https://bugzilla.novell.com/show_bug.cgi?id=790557#c5
--- Comment #5 from Donovan Cameron 2012-12-01 02:02:33 UTC ---
In /etc/init.d/fail2ban,
FAIL2BAN_CONFIG="/etc/sysconfig/fail2ban"
and inside that file is where FAIL2BAN_OPTIONS is defined.
So I placed "-x" into the /etc/sysconfig/fail2ban file so that it's used when
$(/sbin/startproc $FAIL2BAN_CLI -q $FAIL2BAN_OPTIONS start &>/dev/null 2>&1) is
called. Haven't tested this out to see if this solves the failed start...
Do I need to actually define FAIL2BAN_OPTIONS inside /etc/init.d/fail2ban for
it to actually work though...
@frederic,
Does the variable below, which is already in /etc/init.d/fail2ban good enough
to help systemd monitor fail2ban pid?
Or is there something else that needs to get added to the script? Sorry, I
don't know where/what the LSB header is... Still learning lots about linux.
FAIL2BAN_PID="$FAIL2BAN_SOCKET_DIR/fail2ban.pid"
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.