| #
933bee76 |
| 09-May-2023 |
Andrew Geissler <geissonator@yahoo.com> |
systemd: no installation in templated targets
Upstream yocto introduced a change via e510222 (systemd-systemctl:
fix instance template WantedBy symlink construction).
This fixes a bug that we in Op
systemd: no installation in templated targets
Upstream yocto introduced a change via e510222 (systemd-systemctl:
fix instance template WantedBy symlink construction).
This fixes a bug that we in OpenBMC had been taking advantage of in that
we were able to document our templated target dependencies without it
actually doing anything. The real installation of services within
targets occurs in our bitbake recipes due to the complexity of chassis
and host instances on a per machine basis.
Leave the dependency information in the service files but comment them
out. It's useful to be able to look at a service and understand which
targets it's going to be installed into by the bitbake recipes.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I58b4e0f280bcf0268a737aec2613f2d6ca8c8eba
show more ...
|
| #
1af14431 |
| 12-Sep-2022 |
Jayanth Othayoth <ojayanth@in.ibm.com> |
PHAL: add clock data logger service
Service to create informational log daily, which includes clock
register data. This data is used for clock failure debug.
This service will start after start ho
PHAL: add clock data logger service
Service to create informational log daily, which includes clock
register data. This data is used for clock failure debug.
This service will start after start host completion.
Tested: Verified service starts on every boot after
chassis powered-on and start host completion.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I49ea6bfcf886bd5ccf9fb1d042426906bd90a2d3
show more ...
|