prettier: re-format
Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.
Change-Id: If239af03429eca4b6270e329e4a7b100d00f3070
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
diff --git a/README.md b/README.md
index b9a0629..ee56a27 100644
--- a/README.md
+++ b/README.md
@@ -2,16 +2,16 @@
### Overview
-The SEL Logger daemon handles all requests to add new IPMI SEL records
-to the journal. SEL records stored in the journal are identified by
-the standard **MESSAGE\_ID** metadata. Other metadata fields are used to
-store event-specific information for each record.
+The SEL Logger daemon handles all requests to add new IPMI SEL records to the
+journal. SEL records stored in the journal are identified by the standard
+**MESSAGE_ID** metadata. Other metadata fields are used to store event-specific
+information for each record.
### Metadata
-SEL records are identified in the journal using the **MESSAGE\_ID** field.
+SEL records are identified in the journal using the **MESSAGE_ID** field.
-The **MESSAGE\_ID** for SEL records is **"b370836ccf2f4850ac5bee185b77893a"**.
+The **MESSAGE_ID** for SEL records is **"b370836ccf2f4850ac5bee185b77893a"**.
The additional metadata fields for a SEL record are
@@ -27,33 +27,33 @@
### Interface
-The SEL Logger daemon exposes an interface for manually adding System
-and OEM type SEL events, and provides the capability to monitor for
-types of events and log them automatically.
+The SEL Logger daemon exposes an interface for manually adding System and OEM
+type SEL events, and provides the capability to monitor for types of events and
+log them automatically.
The interface for System type events requires
-* A text message to include in the journal entry
-* The sensor path
-* Up to three bytes of SEL data
-* The direction of the event (assertion or deassertion)
-* The generator ID of the requester
+- A text message to include in the journal entry
+- The sensor path
+- Up to three bytes of SEL data
+- The direction of the event (assertion or deassertion)
+- The generator ID of the requester
The interface for OEM type events requires
-* A text message to include in the journal entry
-* Up to thirteen bytes of SEL data (depending on the record type)
-* The record type
+- A text message to include in the journal entry
+- Up to thirteen bytes of SEL data (depending on the record type)
+- The record type
-The **MESSAGE\_ID** and **IPMI\_SEL\_RECORD\_ID** metadata fields are added by the
+The **MESSAGE_ID** and **IPMI_SEL_RECORD_ID** metadata fields are added by the
daemon.
### Event Monitoring
-The SEL Logger daemon can be configured to watch for specific types of events and
-automatically log SEL records for them.
+The SEL Logger daemon can be configured to watch for specific types of events
+and automatically log SEL records for them.
As an example, the SEL Logger has a "threshold event monitor" which implements a
D-Bus match for any "PropertiesChanged" event on the
-"xyz.openbmc_project.Sensor.Threshold" interface. The handler then checks for any
-new threshold events and logs SEL records accordingly.
+"xyz.openbmc_project.Sensor.Threshold" interface. The handler then checks for
+any new threshold events and logs SEL records accordingly.