systemdsystemdDeveloperLennartPoetteringlennart@poettering.netsystemd1systemdsystemd System and Session Managersystemd OPTIONSinit OPTIONSCOMMANDDescriptionsystemd is a system and session manager for
Linux operating systems. When run as first process on
boot (as PID 1) it may act as init system that brings
up and maintains userspace.For compatibility with SysV if systemd is called
as init and a PID that is not
1 it will execute telinit and pass
all command line arguments unmodified. That means
init and telinit
are mostly equivalent when invoked from normal login sessions. See
telinit8
for more information.OptionsThe following options are understood:Prints a short help
text and exits.Set default unit to
activate on startup. If not specified
defaults to
default.target.Tell systemd to run in
a particular mode. Argument is one of
,
. Normally it
should not be necessary to pass this
option, as systemd automatically
detects the mode it is started
in. This call is hence of little use
except for
debugging.Determine startup
sequence, dump it and exit. This is an
option useful for debugging
only.Dump understood unit
configuration items. This outputs a
terse but complete list of
configuration items understood in unit
definition files.Ask for confirmation when spawning processes.Extract D-Bus
interface introspection data. This is
mostly useful at build ot install time
to generate data suitable for the
D-Bus interfaces
repository. Optionally the interface
name for the introspection data may be
specified. If omitted the
introspection data for all interfaces
is dumped.Set log level. As
argument this accepts a numerical log
level or the well-known syslog3
symbolic names (lowercase):
,
,
,
,
,
,
,
.Set log
target. Argument must be one of
,
,
,
,
.Highlight important
log messages. Argument is a boolean
value. If the argument is omitted it
defaults to
.Include code location
in log messages. This is mostly
relevant for debugging
purposes. Argument is a boolean
value. If the argument is omitted
it defaults to
.DirectoriesSystem unit directoriesThe systemd system
manager reads unit configuration from
various directories. Packages that
want to install unit files shall place
them in the directory returned by
pkg-config systemd
--variable=systemdsystemunitdir. Other
directories checked are
/usr/local/share/systemd/system
and
/usr/share/systemd/system. User
configuration always takes
precedence. pkg-config
systemd
--variable=systemdsystemconfdir
returns the path of the system
configuration directory. Packages
should alter this directory only with
the
systemd-install1
tool.Session unit directoriesSimilar rules apply
for the session unit
directories. However, here the XDG
Base Directory specification
is followed to find
units. Applications should place their
unit files in the directory returned
by pkg-config systemd
--variable=systemdsessionunitdir. Global
configuration is done in the
directory reported by
pkg-config systemd
--variable=systemdsessionconfdir. The
systemd-install1
tool can handle both global (i.e. for
all users) and private (for one user)
enabling/disabling of
units.SysV init scripts directoryThe location of the
SysV init script directory varies
between distributions. If systemd
cannot find a native unit file for a
requested service it will look for a
SysV init script of the same name
(with the
.service suffix
removed).SysV runlevel link farm directoryThe location of the
SysV runlevel link farm directory
varies between distributions. systemd
will take the link farm into account
when figuring out whether a service
shall be enabled. Note that a service
unit with a native unit configuration
file can be started by activating it
in the SysV runlevel link
farm.SignalsSIGTERMUpon receiving this
signal the systemd system manager
serializes its state, reexecutes
itself and deserializes the saved
state again. This is mostly equivalent
to systemctl
daemon-reexec.systemd session managers will
start the
exit.target unit
when this signal is received. This is
mostly equivalent to
systemctl --session start
exit.target.SIGINTUpon receiving this
signal the systemd system manager will
start the
ctrl-alt-del.target unit. This
is mostly equivalent to
systemctl start
ctl-alt-del.target.systemd session managers
treat this signal the same way as
SIGTERM.SIGWINCHWhen this signal is
received the systemd system manager
will start the
kbrequest.target
unit. This is mostly equivalent to
systemctl start
kbrequest.target.This signal is ignored by
systemd session
managers.SIGPWRWhen this signal is
received the systemd manager
will start the
sigpwr.target
unit. This is mostly equivalent to
systemctl start
sigpwr.target.SIGUSR1When this signal is
received the systemd manager will try
to reconnect to the D-Bus
bus.SIGUSR2When this signal is
received the systemd manager will log
its complete state in human readable
form. The data logged is the same as
printed by systemctl
dump.SIGHUPReloads the complete
daemon configuration. This is mostly
equivalent to systemctl
daemon-reload.SIGRTMIN+0Enters default mode, starts the
default.target
unit. This is mostly equivalent to
systemctl start
default.target.SIGRTMIN+1Enters rescue mode,
starts the
rescue.target
unit. This is mostly equivalent to
systemctl isolate
rescue.target.SIGRTMIN+2Enters emergency mode,
starts the
emergency.service
unit. This is mostly equivalent to
systemctl isolate
emergency.service.SIGRTMIN+3Halts the machine,
starts the
halt.target
unit. This is mostly equivalent to
systemctl start
halt.target.SIGRTMIN+4Powers off the machine,
starts the
poweroff.target
unit. This is mostly equivalent to
systemctl start
poweroff.target.SIGRTMIN+5Reboots the machine,
starts the
reboot.target
unit. This is mostly equivalent to
systemctl start
reboot.target.Environment$SYSTEMD_LOG_LEVELsystemd reads the
log level from this environment
variable. This can be overriden with
.$SYSTEMD_LOG_TARGETsystemd reads the
log target from this environment
variable. This can be overriden with
.$SYSTEMD_LOG_COLORControls whether
systemd highlights important log
messages. This can be overriden with
.$SYSTEMD_LOG_LOCATIONControls whether
systemd prints the code location along
with log messages. This can be
overriden with
.$XDG_CONFIG_HOME$XDG_CONFIG_DIRS$XDG_DATA_HOME$XDG_DATA_DIRSThe systemd session
manager uses these variables in
accordance to the XDG
Base Directory specification
to find its configuration.$SYSTEMD_UNIT_PATHControls where systemd
looks for unit
files.$SYSTEMD_SYSVINIT_PATHControls where systemd
looks for SysV init scripts.$SYSTEMD_SYSVRCND_PATHControls where systemd
looks for SysV init script runlevel link
farms.$LISTEN_PID$LISTEN_FDSSet by systemd for
supervised processes during
socket-based activation. See
sd_listen_fds3
for more information.
$NOTIFY_SOCKETSet by systemd for
supervised processes for status and
start-up completion notification. See
sd_notify3
for more information.
Sockets and FIFOs@/org/freedesktop/systemd1/notifyDaemon status
notification socket. This is an AF_UNIX
datagram socket in the Linux abstract
namespace, and is used to implement
the daemon notification logic as
implemented by
sd_notify3.@/org/freedesktop/systemd1/loggerUsed internally by the
systemd-logger.service
unit to connect STDOUT and/or STDERR
of spawned processes to
syslog3
or the kernel log buffer. This is an
AF_UNIX stream socket in the Linux
abstract namespace.@/org/freedesktop/systemd1/privateUsed internally as
communication channel between
systemctl1
and the systemd process. This is an
AF_UNIX stream socket in the Linux
abstract namespace. This interface is
private to systemd and should not be
used in external
projects./dev/initctlLimited compatibility
support for the SysV client interface,
as implemented by the
systemd-initctl.service
unit. This is a named pipe in the file
system. This interface is obsolete and
should not be used in new
applications.See Alsosystemctl1,
systemadm1,
systemd-install1,
systemd-notify1,
daemon7,
sd-daemon7,
systemd.unit5,
systemd.special5,
pkg-config1