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.
(From meta-openpower rev: dc61895cbd6b269ed925fdb6266973a98f8a1d8e)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic9741234c9b0a4f7b1c020492a611da21f956d4f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-openpower/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh b/meta-openpower/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh
index 401dd9d..62284d1 100644
--- a/meta-openpower/recipes-phosphor/network/first-boot-set-hostname/first-boot-set-hostname.sh
+++ b/meta-openpower/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