commit | 8d16554c89b1a0ccd0785e06d48114f635ca5c4f | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Wed Sep 07 11:05:26 2022 -0400 |
committer | Andrew Geissler <geissonator@yahoo.com> | Wed Sep 07 11:09:23 2022 -0400 |
tree | ba7e2b8ea48b692e288e28e31fbcbaebbd9cb454 | |
parent | 124e63beaf84a848d51daaf73065860ec6a0482d [diff] |
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
Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture
To build this package, do the following steps:
meson build
ninja -C build
To clean the repository run rm -r build
.