suricata: use KILL is suricata not shut down normal.
sometimes suricata hung and lock the pidfile at suricata stop. Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
This commit is contained in:
parent
b3bc092dad
commit
57fda8c8ad
|
@ -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
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue