| commit | bace99eb318f88adde3a45c12b4ec3507be7d866 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 30 11:37:38 2024 -0400 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 30 11:50:25 2024 -0400 |
| tree | cfa74e8371ee41fe5fdfaaf23d66725cd2dbfe2b | |
| parent | de87972682912d5f50dc31d313aa7505e7325070 [diff] |
OWNERS: add geissonator as maintainer The service-config-manager repository has mostly been in maintenance mode and there has been a bit of a struggle getting general maintenance commits through. I plan on doing some work within this repository and have been reviewing it for a while now. I would be happy to assist with review and merges in this repository. Change-Id: I417984a8adccc377ee77433654ac1ced8642e676 Signed-off-by: Andrew Geissler <geissonator@yahoo.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: