1DBUS-BROKER-LAUNCH(1) User Commands DBUS-BROKER-LAUNCH(1)
2
6 dbus-broker-launch - Launcher for D-Bus Message Brokers
7
9 dbus-broker-launch [ OPTIONS ]
10 dbus-broker-launch --version
11 dbus-broker-launch --help
12
15 dbus-broker-launch is a launcher for dbus-broker, spawning and managing
16 a D-Bus Message Bus. The launcher aims to be fully compatible to the
17 D-Bus reference implementation dbus-daemon(1), supporting the same con‐
18 figuration syntax and runtime environment.
19 Each instance of dbus-broker-launch manages exactly one message bus.
21 Each message bus is independent. The configuration file can either be
22 specified via the command-line, or the default is picked from
23 /usr/share/dbus-1/. Nearly all of the configuration attributes are sup‐
24 ported. See dbus-daemon(1) for details on the configuration syntax.
25
27 The following command-line options are supported. If an option is
28 passed, which is not listed here, the launcher will deny startup and
29 exit with an error.
30 -h, --help
32 print usage information and exit immediately
33 --version
35 print build-version and exit immediately
36 --audit
38 enable logging to the linux audit subsystem (no-op if audit sup‐
39 port was not compiled in; Default: off)
40 --config-file=PATH
42 config file to use (Default: /usr/share/dbus-1/{system,ses‐
43 sion}.conf)
44 --scope=SCOPE
46 select scope to run in (one of: system, user; Default: system)
47
49 By default, dbus-broker-launch logs messages to the system journal. The
50 messages are augmented with lots of metadata, so be sure to check the
51 additional journal-fields. The human-readable log-message is intention‐
52 ally kept short.
53 On startup and shutdown, the launcher logs initial messages that con‐
55 tain information on the parsed configuration files and service defini‐
56 tions. No other log-messages are generated, except those originating in
57 dbus-broker(1).
58
60 Unlike dbus-daemon(1), dbus-broker-launch activates all services as
61 systemd units. Services that already come with a systemd-unit are acti‐
62 vated as usual, but services that lack a systemd unit are activated as
63 transient unit, with an ad-hoc unit-file generated at runtime. This
64 guarantees that all services run in a well-defined environment.
65 The --scope parameter defines which systemd instance the launcher shall
67 use to activate services. In case of system, the launcher will use the
68 system instance of systemd. In case of user, the user instance is used
69 instead.
70 Furthermore, the selected scope also defines which configuration file
72 is used if none is specified on the command-line.
73 The selected scope does not have any further effect. It is only needed
75 to define the activation environment for loaded service definitions. If
76 no activatable services are declared, the scope will have no effect at
77 all.
78
80 The socket to listen on for client connections must be created and
81 passed to dbus-broker-launch by its parent process. The protocol must
82 follow the socket-activation as defined by systemd.socket(1). Only a
83 single socket is supported right now.
84 Additional <listen>%path%</listen> attributes in the configuration are
86 ignored.
87
89 The launcher needs read-access to its configuration file. Other than
90 that, no privileges are needed. If the <user>%user%</user> configura‐
91 tion attribute is used, the launcher will drop privileges when execut‐
92 ing dbus-broker.
93 If activatable services are declared, the launcher will need access to
95 the corresponding systemd instance. The launcher must be allowed to
96 spawn transient units, as well as manage units declared in the service
97 definitions.
98
100 dbus-daemon(1) dbus-broker(1)
101 DBUS-BROKER-LAUNCH(1)