Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / service-config-manager / ba287d8af5414d28ab009eea63070eaf80755484
commitba287d8af5414d28ab009eea63070eaf80755484[log] [tgz]
authorEd Tanous <edtanous@google.com>Wed Mar 01 10:42:28 2023 -0800
committerEd Tanous <edtanous@google.com>Wed Mar 01 10:43:30 2023 -0800
tree3b684f52de704262c67c5f3f4d0589b0841f5c60
parent7a0aac564196c9edae7da3d3073b0eb3940df6f3 [diff]
Change io_service to io_context

This was renamed a while back in boost to be compliant with the
std::executors proposal.

Change-Id: Ie95657cdff79b725d189ee0b36de72813248b52e
Signed-off-by: Ed Tanous <edtanous@google.com>
1 file changed
tree: 3b684f52de704262c67c5f3f4d0589b0841f5c60
  1. inc/
  2. src/
  3. subprojects/
  4. .clang-format
  5. .gitignore
  6. LICENSE
  7. meson.build
  8. meson_options.txt
  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.