| commit | cb6bc03cef3d4acc59f64ab8d628a8e208f6760d | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <andrewg@us.ibm.com> | Wed May 31 20:28:23 2017 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat Jun 03 12:57:46 2017 +0000 |
| tree | b5d1e074812f67a9df59cdd87e4c4c33eaaccf76 | |
| parent | aa8daffd6b7ce409012cbc2b0fe2b3f98824f774 [diff] |
Ensure soft poweroff service stopped on host start There are some error scenarios where the soft poweroff application/service can get stuck waiting for the OS to shut down(45 min). If the user forces a power off and then powers back on, we just need to be sure to stop this service. Change-Id: I7518d5059cfab122f5ded86e9b66d01d2029508a Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
diff --git a/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-host/xyz.openbmc_project.Ipmi.Internal.SoftPowerOff.service b/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-host/xyz.openbmc_project.Ipmi.Internal.SoftPowerOff.service index 2f61b07..7aee76f 100644 --- a/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-host/xyz.openbmc_project.Ipmi.Internal.SoftPowerOff.service +++ b/meta-phosphor/common/recipes-phosphor/ipmi/phosphor-ipmi-host/xyz.openbmc_project.Ipmi.Internal.SoftPowerOff.service
@@ -4,6 +4,7 @@ After=mapper-wait@-org-openbmc-HostIpmi-1.service Wants=obmc-host-stopping@0.target Before=obmc-host-stopping@0.target +Conflicts=obmc-host-start@0.target ConditionPathExists=!/run/openbmc/host@0-request [Service]