ensure disable of reboot occurs after enable
Seen a few instances where both the enable and disable service seem to
get queued up at the same time (at least so close together that systemd
sees them as being requested to run at the same time). This results in a
race condition on which runs first. Bad things happen if the disable
happens to get called before the enable.
Put an explicit dependency in the services so if they are both queued at
the same time, they are run in the correct order.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I0c7a04ede468e200b7fa2ca8184907ebeaf82d5d
diff --git a/reboot-guard-disable.service.in b/reboot-guard-disable.service.in
index 70d702f..3dd2468 100644
--- a/reboot-guard-disable.service.in
+++ b/reboot-guard-disable.service.in
@@ -1,5 +1,6 @@
[Unit]
Description=Removes the guard that blocks BMC reboot
+After=reboot-guard-enable.service
[Service]
Type=oneshot
diff --git a/reboot-guard-enable.service.in b/reboot-guard-enable.service.in
index 7bd2873..0e93d7c 100644
--- a/reboot-guard-enable.service.in
+++ b/reboot-guard-enable.service.in
@@ -1,5 +1,6 @@
[Unit]
Description=Enable a guard that blocks BMC reboot
+Before=reboot-guard-disable.service
[Service]
Type=oneshot