Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / service-config-manager / eca056ed16904e9b83d8ab9ba89ed4de250b5425
commiteca056ed16904e9b83d8ab9ba89ed4de250b5425[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Mon Mar 21 10:16:38 2022 -0500
committerPatrick Williams <patrick@stwcx.xyz>Mon Mar 21 10:16:40 2022 -0500
tree8518128a0e76f4dfff504923c58b9999557696da
parentef5ceced0bee522da0fce5c759b9b733298d82bd [diff]
meson: simplify dependencies

Leverage wrapfile `[provide]` directives to simplify the dependency
searching in the meson.build.

Change-Id: I3ffeb36c566eed00a6070b6c823d9a7b2a8bfbc2
4 files changed
tree: 8518128a0e76f4dfff504923c58b9999557696da
  1. inc/
  2. src/
  3. subprojects/
  4. .clang-format
  5. .gitignore
  6. LICENSE
  7. MAINTAINERS
  8. meson.build
  9. meson_options.txt
  10. OWNERS
  11. README.md
  12. 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.