From d922552198d16b38bc6f72c1cd1ae515b90c9806 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Fri, 15 May 2015 23:36:34 +0200 Subject: [PATCH] rpm: ensure that all the services are enabled after upgrade Especially when some new service was introduced in the meantime. For example this happened between R2 and R3.x release. --- rpm_spec/core-vm.spec | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/rpm_spec/core-vm.spec b/rpm_spec/core-vm.spec index 825db6c..29266f6 100644 --- a/rpm_spec/core-vm.spec +++ b/rpm_spec/core-vm.spec @@ -595,9 +595,13 @@ The Qubes core startup configuration for SystemD init. if [ $1 -eq 1 ]; then /bin/systemctl --no-reload preset-all else - for srv in qubes-dvm qubes-sysinit qubes-misc-post qubes-mount-home qubes-netwatcher qubes-network qubes-qrexec-agent; do - /bin/systemctl --no-reload preset $srv + services="qubes-dvm qubes-misc-post qubes-firewall qubes-mount-home" + services="$services qubes-netwatcher qubes-network qubes-sysinit" + services="$services qubes-update-check qubes-updates-proxy qubes-qrexec-agent" + for srv in $services; do + /bin/systemctl --no-reload preset $srv.service done + /bin/systemctl --no-reload preset qubes-update-check.timer fi # Set default "runlevel"