| commit | 0ad04627de41c6ad2e52500b312bacc4fe54d39e | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Wed Aug 16 10:14:18 2023 +0800 |
| committer | George Liu <liuxiwei@inspur.com> | Wed Aug 16 10:14:18 2023 +0800 |
| tree | fe65715b42a0ffe31a032239e5369a472fbc051d | |
| parent | 70c78fe409453a0590d0a93f0a0503d6c30d5118 [diff] |
meson_options.txt: Support for reading options from meson.options Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts. [1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I93dec606f71f1bccc1e78cc892aeadb96394f125
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: