| commit | b5aabea410ec241bfe23b90ef3bc4ae51cd57c52 | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Mon Nov 11 07:50:14 2024 -0600 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Mon Nov 18 08:08:04 2024 +0000 |
| tree | 53c294842ddcf43b2ff8d2bc1dc729e1e173a849 | |
| parent | 1bfadda6b41ee31a70e4fa0f0829ab109f94f029 [diff] |
boost version 1.86 support Added fix for boost::asio::spawn overload issue reported similar to chriskohlhoff/asio#1524, during boost 1.86 migration build. Proposed fix is to use default completion token. Tested: verified build Change-Id: I469a0c6eb8faac68d6b8ba4c4d3ef86838270eff Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
The service config manager provides a D-Bus interface to manage BMC services as described by the service management D-Bus interfaces.
The configuration settings are intended to persist across BMC reboots.
An example use case for this service is BMCWeb's implementation of the Redfish NetworkProtocol schema.
Implementation details are described in the D-Bus interface README.
The service config manager generally makes configuration changes to systemd units via D-Bus interfaces.
The design pattern to add new services or controls is:
Running and Enabled properties of a service: