Hello community,

here is the log from the commit of package fail2ban for openSUSE:Factory 
checked in at 2012-08-07 21:51:37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/fail2ban (Old)
 and      /work/SRC/openSUSE:Factory/.fail2ban.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "fail2ban", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/fail2ban/fail2ban.changes        2012-06-05 
15:30:21.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.fail2ban.new/fail2ban.changes   2012-08-07 
21:51:39.000000000 +0200
@@ -1,0 +2,6 @@
+Tue Jul 31 16:18:11 CEST 2012 - [email protected]
+
+- Adding to fail2ban.init remove of pid and sock files on stop 
+  in case not removed before (prevents start fail)
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ fail2ban.init ++++++
--- /var/tmp/diff_new_pack.NIZiZC/_old  2012-08-07 21:51:40.000000000 +0200
+++ /var/tmp/diff_new_pack.NIZiZC/_new  2012-08-07 21:51:40.000000000 +0200
@@ -26,6 +26,7 @@
 FAIL2BAN_CONFIG="/etc/sysconfig/fail2ban"
 FAIL2BAN_SOCKET_DIR="/var/run/fail2ban"
 FAIL2BAN_SOCKET="$FAIL2BAN_SOCKET_DIR/fail2ban.sock"
+FAIL2BAN_PID="$FAIL2BAN_SOCKET_DIR/fail2ban.pid"
 
 if [ -e $FAIL2BAN_CONFIG ]; then
        . $FAIL2BAN_CONFIG
@@ -56,6 +57,18 @@
        ## Stop daemon with built-in functionality 'stop'
        /sbin/startproc -w $FAIL2BAN_CLI -q stop > /dev/null 2>&1
 
+       if [ -f $FAIL2BAN_SOCKET ]
+         then
+         echo "$FAIL2BAN_SOCKET  not removed .. removing .." 
+         rm $FAIL2BAN_SOCKET
+        fi
+        if [ -f $FAIL2BAN_PID ]
+         then
+         echo "$FAIL2BAN_PID  not removed .. removing .." 
+         rm $FAIL2BAN_PID
+        fi
+
+
        rc_status -v
        ;;
     try-restart|condrestart)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to