Searched hist:c50e9bad (Results 1 – 4 of 4) sorted by relevance
| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-chassis-poweroff@.target | c50e9bad Tue Jan 26 13:34:21 CST 2021 Andrew Geissler <geissonator@yahoo.com> ensure synch targets started by execution targets
Some systemd services within OpenBMC are run in multiple targets, or
sometimes in standalone situations. When those services are run as a
part of a target, they sometimes need to ensure they run before or after
a synchronization target. They can utilize the Before/After directive
for this but they need assurance the target has been started (i.e.
Wants).
They do not want to put the Wants relationship in their service file
because they do not know the target they are in or if they are being run
as a standalone service via the command line. Starting a synchronization
target outside of the target it is meant for could have impacts on power
on or off operations.
To ensure the synchronization targets are started in the appropriate
situations, add them to the main power on and off targets directly.
Testing:
- Built image, verified basic boot and power off
- Ran HW CI tests and verified they passed
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I558e1c7df57c5543fd0db4d965fe2422ffd83f41
|
| H A D | obmc-host-startmin@.target | c50e9bad Tue Jan 26 13:34:21 CST 2021 Andrew Geissler <geissonator@yahoo.com> ensure synch targets started by execution targets
Some systemd services within OpenBMC are run in multiple targets, or
sometimes in standalone situations. When those services are run as a
part of a target, they sometimes need to ensure they run before or after
a synchronization target. They can utilize the Before/After directive
for this but they need assurance the target has been started (i.e.
Wants).
They do not want to put the Wants relationship in their service file
because they do not know the target they are in or if they are being run
as a standalone service via the command line. Starting a synchronization
target outside of the target it is meant for could have impacts on power
on or off operations.
To ensure the synchronization targets are started in the appropriate
situations, add them to the main power on and off targets directly.
Testing:
- Built image, verified basic boot and power off
- Ran HW CI tests and verified they passed
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I558e1c7df57c5543fd0db4d965fe2422ffd83f41
|
| H A D | obmc-host-stop@.target | c50e9bad Tue Jan 26 13:34:21 CST 2021 Andrew Geissler <geissonator@yahoo.com> ensure synch targets started by execution targets
Some systemd services within OpenBMC are run in multiple targets, or
sometimes in standalone situations. When those services are run as a
part of a target, they sometimes need to ensure they run before or after
a synchronization target. They can utilize the Before/After directive
for this but they need assurance the target has been started (i.e.
Wants).
They do not want to put the Wants relationship in their service file
because they do not know the target they are in or if they are being run
as a standalone service via the command line. Starting a synchronization
target outside of the target it is meant for could have impacts on power
on or off operations.
To ensure the synchronization targets are started in the appropriate
situations, add them to the main power on and off targets directly.
Testing:
- Built image, verified basic boot and power off
- Ran HW CI tests and verified they passed
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I558e1c7df57c5543fd0db4d965fe2422ffd83f41
|
| H A D | obmc-chassis-poweron@.target | c50e9bad Tue Jan 26 13:34:21 CST 2021 Andrew Geissler <geissonator@yahoo.com> ensure synch targets started by execution targets
Some systemd services within OpenBMC are run in multiple targets, or
sometimes in standalone situations. When those services are run as a
part of a target, they sometimes need to ensure they run before or after
a synchronization target. They can utilize the Before/After directive
for this but they need assurance the target has been started (i.e.
Wants).
They do not want to put the Wants relationship in their service file
because they do not know the target they are in or if they are being run
as a standalone service via the command line. Starting a synchronization
target outside of the target it is meant for could have impacts on power
on or off operations.
To ensure the synchronization targets are started in the appropriate
situations, add them to the main power on and off targets directly.
Testing:
- Built image, verified basic boot and power off
- Ran HW CI tests and verified they passed
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I558e1c7df57c5543fd0db4d965fe2422ffd83f41
|