интерфейс D-Bus системы systemd (The D-Bus interface of systemd)
Вступление (Introduction)
systemd(1) and its auxiliary daemons expose a number of APIs over
D-Bus. This page only describes the various APIs exposed by the
system and service manager itself. It does not cover the
auxiliary daemons.
The service manager exposes a number of objects on the bus: one
Manager object as a central entry point for clients along with
individual objects for each unit and for each queued job. The
unit objects each implement a generic Unit interface as well as a
type-specific interface. For example, service units implement
both org.freedesktop.systemd1.Unit and
org.freedesktop.system1.Service. The manager object can list unit
and job objects or directly convert a unit name or job id into a
bus path of the corresponding D-Bus object.
Properties exposing time values are usually encoded in
microseconds (usec) on the bus, even if their corresponding
settings in the unit files are in seconds.
In contrast to most of the other services of the systemd suite,
PID 1 does not use polkit
[1] for controlling access to privileged
operations, but relies exclusively on the low-level D-Bus policy
language. (This is done in order to avoid a cyclic dependency
between polkit and systemd/PID 1.) This means that sensitive
operations exposed by PID 1 on the bus are generally not
available to unprivileged processes directly. However, some
operations (such as shutdown/reboot/suspend) are made available
through the D-Bus API of logind, see org.freedesktop.login1(5).