Core Update 171: Stop Apache before applying the upgrade

Since we replace Perl, users most likely get to see some nasty "Internal
Server Error" messages during the upgrade. To suppres them, and to limit
the chance of side effects, stop Apache before applying the update, and
start it again afterwards.

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

diff --git a/config/rootfiles/core/171/update.sh b/config/rootfiles/core/171/update.sh
index 8a6c197101d72a0dd4d92eaefe16a5b024550e44..48fd742b567e09806d136af3c9ccd089fe819230 100644 (file)
--- a/config/rootfiles/core/171/update.sh
+++ b/config/rootfiles/core/171/update.sh
@@ -32,6 +32,7 @@ for (( i=1; i<=$core; i++ )); do
 done
 
 # Stop services
+/etc/rc.d/init.d/apache stop
 /etc/rc.d/init.d/squid stop
 /etc/rc.d/init.d/openvpn stop
 /etc/rc.d/init.d/ipsec stop
@@ -148,14 +149,13 @@ ldconfig
 /usr/local/bin/filesystem-cleanup
 
 # Start services
+/etc/rc.d/init.d/apache start
 if grep -q "ENABLED=on" /var/ipfire/ovpn/settings; then
        /etc/init.d/openvpn start
 fi
-
 if grep -q "ENABLED=on" /var/ipfire/vpn/settings; then
        /etc/init.d/ipsec start
 fi
-
 if -f /var/ipfire/proxy/enable; then
        /etc/init.d/squid start
 fi