| commit | 430d7ea571104ac6839a41acb2ed6eebcd5f5f09 | [log] [tgz] |
|---|---|---|
| author | Jiaqing Zhao <jiaqing.zhao@intel.com> | Fri Apr 01 23:23:25 2022 +0800 |
| committer | Jiaqing Zhao <jiaqing.zhao@intel.com> | Tue Apr 05 19:18:20 2022 +0800 |
| tree | 10a09e3f5fdca1c55b035470a786dfd4d63618a0 | |
| parent | f27f431faa0c40c0253e50cddd92ffcb99081604 [diff] |
Use unit name to distinguish USB code update service In incoming patch, the object path of services will be encoded by sdbusplus, using object path to distinguish the dummy USB code update service is no longer suitable. This patch uses the unit name instead. Tested: Verified modifying the property of USB code update service will use these special handlers as before. Other services are not affected. Change-Id: I9d14ae57ca3f5a68744011e18e3ae45905edcacf 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: