| commit | f27f431faa0c40c0253e50cddd92ffcb99081604 | [log] [tgz] |
|---|---|---|
| author | Jiaqing Zhao <jiaqing.zhao@intel.com> | Sat Apr 02 17:42:46 2022 +0800 |
| committer | Jiaqing Zhao <jiaqing.zhao@intel.com> | Sat Apr 02 17:46:51 2022 +0800 |
| tree | 16e304c50caf3c0f96ef84dc8c54f410e136d135 | |
| parent | eca056ed16904e9b83d8ab9ba89ed4de250b5425 [diff] |
Switch remaining logs to lg2
Since cb267c8 ("logging: switch to lg2"), service-config-manager has
switched to using lg2 for logging, but there are still some old-style
phosphor::logging::log calls. Change them to lg2.
Tested:
Build pass.
Change-Id: I2702e3d57b8f4b9e411c8f20f3f33329e70c8b23
Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.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: