Searched hist:08148283 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/phosphor-state-manager/service_files/ |
| H A D | phosphor-set-chassis-transition-to-off@.service | 08148283 Tue Oct 08 13:45:23 CDT 2024 Andrew Geissler <geissonator@yahoo.com> phosphor-set-chassis-transition: ensure only run once
If a user were to power their system on, and then off, and then off
again, they will see their CurrentPowerState set to TransitioningToOff.
Although it's a bit of an unusual use case, it's fairly common in the
lab/dev environment when users want to quickly ensure their system is in
a powered off or on state (without first looking at its current state).
Similar to what is in the host transition services, ensure we only run
the chassis transition services once per power on or off.
Tested:
- Ensured multiple power off requests will not leave CurrentPowerState
in TransitioningToOff state
Change-Id: I4040072ed0b42f37c9488994b0f7a5975a2bb7c9
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
| H A D | phosphor-set-chassis-transition-to-on@.service | 08148283 Tue Oct 08 13:45:23 CDT 2024 Andrew Geissler <geissonator@yahoo.com> phosphor-set-chassis-transition: ensure only run once
If a user were to power their system on, and then off, and then off
again, they will see their CurrentPowerState set to TransitioningToOff.
Although it's a bit of an unusual use case, it's fairly common in the
lab/dev environment when users want to quickly ensure their system is in
a powered off or on state (without first looking at its current state).
Similar to what is in the host transition services, ensure we only run
the chassis transition services once per power on or off.
Tested:
- Ensured multiple power off requests will not leave CurrentPowerState
in TransitioningToOff state
Change-Id: I4040072ed0b42f37c9488994b0f7a5975a2bb7c9
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|