| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
When a power off or reboot is host initiated, do
not run the soft power off service. Since the host
is the one requesting the action, there's no need to
execute the soft off function (notification to host
to shutdown).
Change-Id: Ia6e833598e6042646e5d5bd17821ed29e141fa6f
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
|
| |
As a part of the soft power off (host-shutdown) ensure
that the host-stop target always gets called. Updated the
involved services to ensure they are run in the correct order.
Change-Id: I7e9113631786f0d0cb0f89b94c4b97fdc0328e7b
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
| |
Change-Id: I9d17bb3b90dee86e2290b8552bb519b0164c477c
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
| |
Change-Id: I31237359991a61f51042df6ce47a7f62286fb665
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
| |
Resolves openbmc/openbmc#1002
Change-Id: Iab57b81f3e65572d09aa126ef4be37460ff9d984
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Attempt at consistant naming convention of ipmi recipes.
Change-Id: I9828503a61bccd83dc0294a3dca2db2d9981593b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|