Hello community,

here is the log from the commit of package fail2ban for openSUSE:11.4
checked in at Thu Dec 1 12:11:47 CET 2011.



--------
--- old-versions/11.4/UPDATES/all/fail2ban/fail2ban.changes     2011-09-01 
16:09:20.000000000 +0200
+++ 11.4/fail2ban/fail2ban.changes      2011-11-25 15:48:43.000000000 +0100
@@ -1,0 +2,5 @@
+Fri Nov 25 13:51:35 UTC 2011 - [email protected]
+
+- Drop stale socket files on startup (bnc#537239, bnc#730044)
+
+-------------------------------------------------------------------

calling whatdependson for 11.4-i586


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

Other differences:
------------------
++++++ fail2ban.spec ++++++
--- /var/tmp/diff_new_pack.XiEp1m/_old  2011-12-01 12:11:30.000000000 +0100
+++ /var/tmp/diff_new_pack.XiEp1m/_new  2011-12-01 12:11:30.000000000 +0100
@@ -26,7 +26,7 @@
 PreReq:         %fillup_prereq
 AutoReqProv:    on
 Version:        0.8.4
-Release:        11.<RELEASE12>
+Release:        11.<RELEASE14>
 Url:            http://www.fail2ban.org/
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildArch:      noarch

++++++ fail2ban.init ++++++
--- /var/tmp/diff_new_pack.XiEp1m/_old  2011-12-01 12:11:30.000000000 +0100
+++ /var/tmp/diff_new_pack.XiEp1m/_new  2011-12-01 12:11:30.000000000 +0100
@@ -50,6 +50,7 @@
 
 # Socket directory
 FAIL2BAN_SOCK_DIR="/var/run/fail2ban"
+FAIL2BAN_SOCK="$FAIL2BAN_SOCK_DIR/fail2ban.sock"
 
 # Read config  
 . $FAIL2BAN_CONFIG
@@ -64,6 +65,11 @@
        if [ ! -d $FAIL2BAN_SOCK_DIR ]; then
                mkdir -p $FAIL2BAN_SOCK_DIR
        fi
+       if [ -e $FAIL2BAN_SOCK ]; then
+               if ! lsof -n $FAIL2BAN_SOCK &>/dev/null; then
+                       rm $FAIL2BAN_SOCK
+               fi
+       fi
        ## Start daemon with startproc(8). If this fails
        ## the return value is set appropriately by startproc.
        startproc $FAIL2BAN_CLI -q $FAIL2BAN_OPTIONS start > /dev/null 2>&1

continue with "q"...



Remember to have fun...

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

Reply via email to