| commit | ee190f032091dda63053a82e90866244f09ed54b | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 29 06:44:55 2023 -0600 |
| committer | AppaRao Puli <apparao.puli@linux.intel.com> | Thu Jun 20 10:37:49 2024 +0000 |
| tree | 14f5caf4bb665e887216836a7d3978d17fe952b9 | |
| parent | 23ecbb6c651b5e323e9b08aa70fbb100f7024482 [diff] |
build: use allowed over enabled Meson feature options are typically in a tri-state of enabled, disabled, or auto. The enabled and disabled functions on an option (from `get_option`) no longer return true for auto features. Instead, the expectation is to use `allowed()` which is true for both enabled and auto. Switch all uses of `enabled` to `allowed`. Change-Id: If4484727bbd187b6fb92b7a0997fb8fcda5aec70 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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: