suricata: use KILL is suricata not shut down normal.
authorArne Fitzenreiter <arne_f@ipfire.org>
Mon, 9 Mar 2020 06:41:32 +0000 (06:41 +0000)
committerArne Fitzenreiter <arne_f@ipfire.org>
Mon, 9 Mar 2020 06:41:32 +0000 (06:41 +0000)
sometimes suricata hung and lock the pidfile at
suricata stop.

Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
config/rootfiles/core/142/filelists/files
src/initscripts/system/suricata

index 11daea4..de55da9 100644 (file)
@@ -5,6 +5,7 @@ var/ipfire/langs
 etc/unbound/unbound.conf
 etc/rc.d/helper/aws-setup
 etc/rc.d/helper/azure-setup
+etc/rc.d/init.d/suricata
 etc/rc.d/init.d/unbound
 etc/suricata/suricata.yaml
 lib/udev/network-hotplug-bridges
index 29e58a7..f0d4b88 100644 (file)
@@ -190,7 +190,10 @@ case "$1" in
                # Flush firewall chain.
                flush_fw_chain
 
-               # Remove suricata control socket.              
+               # Sometimes suricata not correct shutdown. So killall.
+               killall -KILL /usr/bin/suricata 2>/dev/null
+
+               # Remove suricata control socket.
                rm /var/run/suricata/* >/dev/null 2>/dev/null
 
                # Trash remain pid file if still exists.