Core Update 170: Stop Suricata before extracting files

Stopping services before potentially tampering with files they use is a
more sane approach than doing the latter and hope the running service
can cope with it. Suricata, at least, reportedly doesn't.

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>

diff --git a/config/rootfiles/core/170/update.sh b/config/rootfiles/core/170/update.sh
index d9f13d4dec5a4f99acefc8ed26ea6a7aa3722af6..cbac8572e9cbeb14627240120f0aa81522018b8b 100644 (file)
--- a/config/rootfiles/core/170/update.sh
+++ b/config/rootfiles/core/170/update.sh
@@ -45,6 +45,7 @@ done
 
 # Stop services
 /etc/init.d/rc.d/unbound stop
+/etc/init.d/rc.d/suricata stop
 
 KVER="xxxKVERxxx"
 
@@ -171,7 +172,7 @@ sed -i /etc/collectd.conf \
 
 # Start services
 /etc/init.d/rc.d/unbound start
-/etc/init.d/rc.d/suricata restart
+/etc/init.d/rc.d/suricata start
 
 # Harden mount options of /boot
 sed -e -i "s@[[:space:]]*\/boot[[:space:]]*auto[[:space:]]*defaults[[:space:]]*@ \/boot    auto defaults,nodev,noexec,nosuid   @g" /etc/fstab