Do not reload systemd when removing services
Testing has shown that reloading the systemd daemon during the execution
of the multi-user.target can cause intermittent failures. systemctl
itself has special code to handle the situation when it sends the
Reload command to the systemd daemon. It doubles the D-bus timeout and
it also expects a disconnect, not a reply to it's sd_bus_call().
There is no need to have systemd do a daemon-reload with these services.
The goal is to just prevent them from running during the next reboot of
the BMC in which case systemd will be reloading the services anyway.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I4c1970621f46093dfa3719c2746f41d521db63c7
diff --git a/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh b/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh
index 401dd9d..62284d1 100644
--- a/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh
+++ b/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh
@@ -81,4 +81,4 @@
sync_hostname
-systemctl disable first-boot-set-hostname.service
+systemctl --no-reload disable first-boot-set-hostname.service
diff --git a/recipes-phosphor/network/first-boot-set-mac/first-boot-set-mac.sh b/recipes-phosphor/network/first-boot-set-mac/first-boot-set-mac.sh
index cf03b82..da1b305 100755
--- a/recipes-phosphor/network/first-boot-set-mac/first-boot-set-mac.sh
+++ b/recipes-phosphor/network/first-boot-set-mac/first-boot-set-mac.sh
@@ -79,4 +79,4 @@
sync_mac $1
-systemctl disable first-boot-set-mac@${1}.service
+systemctl --no-reload disable first-boot-set-mac@${1}.service