commit | d2a99a4db9db0a80392b4cc40738e91653d54c30 | [log] [tgz] |
---|---|---|
author | Jiaqing Zhao <jiaqing.zhao@intel.com> | Fri Feb 25 17:26:30 2022 +0800 |
committer | Jiaqing Zhao <jiaqing.zhao@intel.com> | Mon Feb 28 15:45:56 2022 +0800 |
tree | 0ffb667680c773bc547e4f14038d63eca8e057a7 | |
parent | aa41e674c2d2119fbabe4e0d6569a493163f337f [diff] |
Ignore non-existent units In systemd, if a non-existent unit is referenced by other unit, it will be listed in ListUnits response. This commit ignores these non-existent entries to prevent performing operations on them. Tested: In dropbear.socket, there is a Conflicts=dropbear.service which creates a non-existent service entry. With this commit, it will not be added to the service object path in /etc/srvcfg-mgr.json. Change-Id: I2ce360ea3a0b10f527672d1601ae4d6234c1a9aa 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: