X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.xml;h=27756723b1535e599ba9de4ac2b22af90d38a694;hp=f754348ce1a06033ba4e4c8ce43005ac1f358c40;hb=af62c704053b5d34672497eb5bdc4764ebbb5f4f;hpb=160cd5c9aa2301892e13950015de7968c764340d
diff --git a/man/systemd.xml b/man/systemd.xml
index f754348ce..27756723b 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -44,6 +44,7 @@
systemd
+ initsystemd System and Session Manager
@@ -61,12 +62,12 @@
systemd 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.
+ boot (as PID 1), it acts as init system that brings
+ up and maintains userspace services.
- For compatibility with SysV if systemd is called
+ For compatibility with SysV, if systemd is called
as init and a PID that is not
- 1 it will execute telinit and pass
+ 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
@@ -122,9 +123,9 @@
Dump understood unit
configuration items. This outputs a
- terse list of configuration items
- understood in unit definition
- files.
+ terse but complete list of
+ configuration items understood in unit
+ definition files.
@@ -136,12 +137,12 @@
Extract D-Bus
interface introspection data. This is
- mostly useful at build ot install time
+ mostly useful at build at 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
+ specified. If omitted, the
introspection data for all interfaces
is dumped.
@@ -192,32 +193,362 @@
it defaults to
.
-
-
Directories
+
+
+
+ System unit directories
+
+ The 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 the content of these directories
+ only with the
+ systemd-install1
+ tool.
+
+
+
+
+
+ Session unit directories
+
+ Similar 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 directory
+
+ The 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 directory
+
+ The 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.
+
+
- Signal
+ Signals
- SIGTERM
+ SIGTERM
+
+ Upon 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.
+
+
+
+ SIGINT
+
+ Upon 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.
+
+
+
+ SIGWINCH
+
+ When 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.
+
+
+
+ SIGPWR
+
+ When this signal is
+ received the systemd manager
+ will start the
+ sigpwr.target
+ unit. This is mostly equivalent to
+ systemctl start
+ sigpwr.target.
+
+
+
+ SIGUSR1
+
+ When this signal is
+ received the systemd manager will try
+ to reconnect to the D-Bus
+ bus.
+
+
+
+ SIGUSR2
+
+ When 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.
+
+
+
+ SIGHUP
+
+ Reloads the complete
+ daemon configuration. This is mostly
+ equivalent to systemctl
+ daemon-reload.
+
+
+
+ SIGRTMIN+0
+
+ Enters default mode, starts the
+ default.target
+ unit. This is mostly equivalent to
+ systemctl start
+ default.target.
+
+
+
+ SIGRTMIN+1
+
+ Enters rescue mode,
+ starts the
+ rescue.target
+ unit. This is mostly equivalent to
+ systemctl isolate
+ rescue.target.
+
- systemd serializes its
- state, reexecutes itself and
- deserializes the saved state
- again. This is mostly equivalent to
- systemctl
- daemon-reexec.
+
+ SIGRTMIN+2
+
+ Enters emergency mode,
+ starts the
+ emergency.service
+ unit. This is mostly equivalent to
+ systemctl isolate
+ emergency.service.
+
+
+
+ SIGRTMIN+3
+
+ Halts the machine,
+ starts the
+ halt.target
+ unit. This is mostly equivalent to
+ systemctl start
+ halt.target.
+
+
+
+ SIGRTMIN+4
+
+ Powers off the machine,
+ starts the
+ poweroff.target
+ unit. This is mostly equivalent to
+ systemctl start
+ poweroff.target.
+
+
+
+ SIGRTMIN+5
+
+ Reboots the machine,
+ starts the
+ reboot.target
+ unit. This is mostly equivalent to
+ systemctl start
+ reboot.target.
+
+ Environment
+
+
+
+ $SYSTEMD_LOG_LEVEL
+ systemd reads the
+ log level from this environment
+ variable. This can be overridden with
+ .
+
+
+
+ $SYSTEMD_LOG_TARGET
+ systemd reads the
+ log target from this environment
+ variable. This can be overridden with
+ .
+
+
+
+ $SYSTEMD_LOG_COLOR
+ Controls whether
+ systemd highlights important log
+ messages. This can be overridden with
+ .
+
+
+
+ $SYSTEMD_LOG_LOCATION
+ Controls whether
+ systemd prints the code location along
+ with log messages. This can be
+ overridden with
+ .
+
+
+
+ $XDG_CONFIG_HOME
+ $XDG_CONFIG_DIRS
+ $XDG_DATA_HOME
+ $XDG_DATA_DIRS
+
+ The systemd session
+ manager uses these variables in
+ accordance to the XDG
+ Base Directory specification
+ to find its configuration.
+
+
+
+ $SYSTEMD_UNIT_PATH
+
+ Controls where systemd
+ looks for unit
+ files.
+
+
+
+ $SYSTEMD_SYSVINIT_PATH
+
+ Controls where systemd
+ looks for SysV init scripts.
+
+
+
+ $SYSTEMD_SYSVRCND_PATH
+
+ Controls where systemd
+ looks for SysV init script runlevel link
+ farms.
+
+
+
+ $LISTEN_PID
+ $LISTEN_FDS
+
+ Set by systemd for
+ supervised processes during
+ socket-based activation. See
+ sd_listen_fds3
+ for more information.
+
+
+
+
+ $NOTIFY_SOCKET
+
+ Set by systemd for
+ supervised processes for status and
+ start-up completion notification. See
+ sd_notify3
+ for more information.
+
+
+
+ Sockets and FIFOs
@@ -278,11 +609,18 @@
-
See Also
+ systemctl1,
+ systemadm1,
+ systemd-install1,
+ systemd-notify1,
daemon7,
+ sd-daemon7,
+ systemd.unit5,
+ systemd.special5,
+ pkg-config1