Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / service-config-manager / refs/heads/master
commit6e046368a2da9f2bd0a33ba12dd61e3c57338ce1[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Thu Jun 12 12:53:20 2025 -0400
committerPatrick Williams <patrick@stwcx.xyz>Thu Jun 12 12:53:20 2025 -0400
tree59a4020e6fdcbd41121685f11532faec9a805b1e
parentc828db702208df9fccd96f8bef036e3f32012bcd [diff]
markdownlint: minor fixes

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ieae39289637a37f7b62f92792dff8255ccb6a04e
1 file changed
tree: 59a4020e6fdcbd41121685f11532faec9a805b1e
  1. inc/
  2. src/
  3. subprojects/
  4. .clang-format
  5. .gitignore
  6. LICENSE
  7. meson.build
  8. meson.options
  9. OWNERS
  10. README.md
  11. srvcfg-manager.service
README.md

Service config manager

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.

Design

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:

  • Determine if the service you want to control is socket activated.
  • To control the Running and Enabled properties of a service:
    • For a service which uses socket activation, control the socket.
    • For other services, control the service unit itself.