| commit | 611de486cc618dab2943ff3a7a8c2fd9e2380cec | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 28 21:38:55 2024 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 28 21:38:58 2024 -0600 |
| tree | 8ccef0a425ccce5f932a458e3a353cf1548f578d | |
| parent | 2d74ceb6260801c0e820c68be8cef035de5d3d7d [diff] |
systemd: Add host identifier to service description
On a multi-host system, there is no identifier for the post code manager
service, so you end up with console messages such as:
```
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
Starting Post code manager...
```
Add an identifier to the templated service file so that these instances
are differentiated.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I63c0a5d80f4870314805b8f9ff07782be9fe3faf
This phosphor-post-code-manager repository provides an infrastructure to persist the POST codes in BMC filesystem & it also owns the systemd services that are responsible for exposing the BIOS Post Codes to rest of the world via redfish.
To build phosphor-post-code-manager package , do the following steps:
meson <build directory> ninja -C <build directory>
This repository ships xyz.openbmc_project.State.Boot.PostCode.service systemd service along with its template version and a tiny binary that exposes the necessary dbus interfaces & methods to extract the POST codes per boot cycle.
This repository is tightly coupled with phosphor-host-postd OpenBMC respository which is responsible for emitting the dbus signals for every new POST Code.
phosphor-post-code-manager is architected to look for the property changed signals which are being emitted from the service that hosts Value property on xyz.openbmc_project.State.Boot.Raw interface & archive them per boot on the filesystem, so that those can be exposed over redfish