openbmc/phosphor-post-code-manager/README.md

1 # phosphor-post-code-manager
3 This phosphor-post-code-manager repository provides an infrastructure to persist
9 To build phosphor-post-code-manager package , do the following steps:
13 ninja -C <build directory>
20 [template version](https://github.com/openbmc/docs/blob/master/designs/multi-host-postcode.md)
22 [dbus interfaces & methods](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xy…
28 [phosphor-host-postd](https://github.com/openbmc/phosphor-host-postd) OpenBMC
32 phosphor-post-code-manager is architected to look for the property changed
34 [Value](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/St…
37 [redfish](https://github.com/openbmc/docs/blob/master/designs/redfish-postcodes.md)
42 specific postcodes. Special handling include starting user configured systemd
43 unit files and/or creating a structured event as defined by the user. The JSON
44 configuration file can be passed in using the `--config PATH` or `-c PATH`
59     "event": {
70 Each entry in the array describes a special handler for a specific post code.
72 - `primary` - [required] The primary post code to match.
73 - `secondary` - [optional] The secondary post code to match. If not present, the
75 - `targets` - [optional] List of systemd targets to start when the matching post
77 - `event` - [optional] The descriptor of the event to create with
78   phosphor-logging.
79   - `event::name` - Name of the event log. See `log-create --list` for a list of
81   - `event::arguments` - The named argument list which will be used to create
82     the event.