.\" Man page generated from reStructuredText.
.
.TH DBUS-BROKER-LAUNCH 1 "" "" "User Commands"
.SH NAME
dbus-broker-launch \- Launcher for D-Bus Message Brokers
.
.nr rst2man-indent-level 0
.
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
-
\\n[rst2man-indent0]
\\n[rst2man-indent1]
\\n[rst2man-indent2]
..
.de1 INDENT
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
..
.de UNINDENT
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
.SH SYNOPSIS
.nf
\fBdbus\-broker\-launch\fP [ OPTIONS ]
\fBdbus\-broker\-launch\fP \fB\-\-version\fP
\fBdbus\-broker\-launch\fP \fB\-\-help\fP
.fi
.sp
.SH DESCRIPTION
.sp
\fBdbus\-broker\-launch\fP is a launcher for \fBdbus\-broker\fP, spawning and managing
a D\-Bus Message Bus. The launcher aims to be fully compatible to the D\-Bus
reference implementation \fBdbus\-daemon\fP(1), supporting the same configuration
syntax and runtime environment.
.sp
Each instance of \fBdbus\-broker\-launch\fP manages exactly one message bus. Each
message bus is independent. The configuration file can either be specified via
the command\-line, or the default is picked from \fI/usr/share/dbus\-1/\fP\&. Nearly
all of the configuration attributes are supported. See \fBdbus\-daemon\fP(1) for
details on the configuration syntax.
.SH OPTIONS
.sp
The following command\-line options are supported. If an option is passed, which
is not listed here, the launcher will deny startup and exit with an error.
.INDENT 0.0
.TP
.B \-h\fP,\fB \-\-help
print usage information and exit immediately
.TP
.B \-\-version
print build\-version and exit immediately
.TP
.B \-\-audit
enable logging to the linux audit subsystem
(no\-op if audit support was not compiled in;
\fBDefault\fP: off)
.TP
.BI \-\-config\-file\fB= PATH
config file to use (\fBDefault\fP:
\fI/usr/share/dbus\-1/{system,session}.conf\fP)
.TP
.BI \-\-scope\fB= SCOPE
select scope to run in (one of: \fIsystem\fP,
\fIuser\fP; \fBDefault\fP: \fIsystem\fP)
.UNINDENT
.SH LOGGING
.sp
By default, \fBdbus\-broker\-launch\fP logs messages to the system journal. The
messages are augmented with lots of metadata, so be sure to check the
additional journal\-fields. The human\-readable log\-message is intentionally kept
short.
.sp
On startup and shutdown, the launcher logs initial messages that contain
information on the parsed configuration files and service definitions. No other
log\-messages are generated, except those originating in \fBdbus\-broker\fP(1).
.SH SCOPE
.sp
Unlike \fBdbus\-daemon\fP(1), \fBdbus\-broker\-launch\fP activates all services as
systemd units. Services that already come with a systemd\-unit are activated as
usual, but services that lack a systemd unit are activated as transient unit,
with an ad\-hoc unit\-file generated at runtime. This guarantees that all
services run in a well\-defined environment.
.sp
The \fB\-\-scope\fP parameter defines which systemd instance the launcher shall use
to activate services. In case of \fIsystem\fP, the launcher will use the system
instance of systemd. In case of \fIuser\fP, the user instance is used instead.
.sp
Furthermore, the selected scope also defines which configuration file is used
if none is specified on the command\-line.
.sp
The selected scope does not have any further effect. It is only needed to
define the activation environment for loaded service definitions. If no
activatable services are declared, the scope will have no effect at all.
.SH SOCKETS
.sp
The socket to listen on for client connections must be created and passed to
\fBdbus\-broker\-launch\fP by its parent process. The protocol must follow the
socket\-activation as defined by \fBsystemd.socket\fP(1). Only a single socket is
supported right now.
.sp
Additional \fI%path%\fP attributes in the configuration are
ignored.
.SH PRIVILEGES
.sp
The launcher needs read\-access to its configuration file. Other than that, no
privileges are needed. If the \fI%user%\fP configuration attribute is
used, the launcher will drop privileges when executing \fBdbus\-broker\fP\&.
.sp
If activatable services are declared, the launcher will need access to the
corresponding systemd instance. The launcher must be allowed to spawn transient
units, as well as manage units declared in the service definitions.
.SH SEE ALSO
.sp
\fBdbus\-daemon\fP(1)
\fBdbus\-broker\fP(1)
.\" Generated by docutils manpage writer.
.