| commit | f476683ce8493f1ae08d09bfaa3d579ffdb316f1 | [log] [tgz] |
|---|---|---|
| author | Jiaqing Zhao <jiaqing.zhao@intel.com> | Mon Feb 28 14:28:18 2022 +0800 |
| committer | Jiaqing Zhao <jiaqing.zhao@intel.com> | Mon Feb 28 15:45:56 2022 +0800 |
| tree | bc290c7f12a26b34b09aabced77b876e39b43ae3 | |
| parent | d2a99a4db9db0a80392b4cc40738e91653d54c30 [diff] |
Improve socket-activated service handling This patch provides a more generic way of handling socket-activated services like dropbear. A socket-activated service only has base socket unit and spawns service unit with instance name on incoming connection, so the instanced units of it need to be ignored. And whether a service is socket-activated can be determined by checking the existance of its service object path. Tested: * Two socket-activated service, dropbear and obmc-console-ssh, can be controlled as expected. * Instances of socket-activated services are no loger added to monitor list. Change-Id: If8faa2248e5794a410f804125410608aa69b858d 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: