X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=acba820fdfb4ff5176fb96c29fe66b19d7768ab4;hb=708c143c7cd2bbd748ac0fa993496ff44e72701c;hp=55ba0875f0e73422536002b1185b3f32c01fd2c7;hpb=08177c85efd52c2c2ab00991791649ad8cf61297;p=elogind.git
diff --git a/man/systemd.xml b/man/systemd.xml
index 55ba0875f..acba820fd 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -78,7 +78,7 @@
the configuration file
system.conf, otherwise
user.conf. See
- systemd.conf5
+ systemd-system.conf5
for more information.
@@ -118,25 +118,11 @@
configuration items understood in unit
definition files.
-
-
-
- Extract D-Bus
- interface introspection data. This is
- mostly useful 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
- introspection data for all interfaces
- is dumped.
- Set default unit to
- activate on startup. If not specified
+ activate on startup. If not specified,
defaults to
default.target.
@@ -233,7 +219,7 @@
Highlight important
log messages. Argument is a boolean
- value. If the argument is omitted it
+ value. If the argument is omitted, it
defaults to
.
@@ -285,25 +271,27 @@
Conceptssystemd provides a dependency system between
- various entities called "units". Units encapsulate
- various objects that are relevant for system boot-up
- and maintenance. The majority of units are configured
- in unit configuration files, whose syntax and basic
- set of options is described in
+ various entities called "units" of 12 different
+ types. Units encapsulate various objects that are
+ relevant for system boot-up and maintenance. The
+ majority of units are configured in unit configuration
+ files, whose syntax and basic set of options is
+ described in
systemd.unit5,
however some are created automatically from other
- configuration or dynamically from system state. Units
- may be 'active' (meaning started, bound, plugged in,
- ... depending on the unit type, see below), or
- 'inactive' (meaning stopped, unbound, unplugged, ...),
- as well as in the process of being activated or
- deactivated, i.e. between the two states (these states
- are called 'activating', 'deactivating'). A special
- 'failed' state is available as well which is very
- similar to 'inactive' and is entered when the service
- failed in some way (process returned error code on
- exit, or crashed, or an operation timed out). If this
- state is entered the cause will be logged, for later
+ configuration, dynamically from system state or
+ programmatically at runtime. Units may be "active"
+ (meaning started, bound, plugged in, ..., depending on
+ the unit type, see below), or "inactive" (meaning
+ stopped, unbound, unplugged, ...), as well as in the
+ process of being activated or deactivated,
+ i.e. between the two states (these states are called
+ "activating", "deactivating"). A special "failed"
+ state is available as well, which is very similar to
+ "inactive" and is entered when the service failed in
+ some way (process returned error code on exit, or
+ crashed, or an operation timed out). If this state is
+ entered, the cause will be logged, for later
reference. Note that the various unit types may have a
number of additional substates, which are mapped to
the five generalized unit states described
@@ -312,7 +300,7 @@
The following unit types are available:
- Service units, which control
+ Service units, which start and control
daemons and the processes they consist of. For
details see
systemd.service5.
@@ -369,6 +357,18 @@
objects change or are modified. See
systemd.path5.
+ Slice units may be used to
+ group units which manage system processes
+ (such as service and scope units) in a
+ hierarchical tree for resource management
+ purposes. See
+ systemd.slice5.
+
+ Scope units are similar to
+ service units, but manage foreign processes
+ instead of starting them as well. See
+ systemd.scope5.
+
Units are named as their configuration
@@ -415,7 +415,7 @@
multi-user.target (for limited
console-only boots for use in embedded or server
environments, or similar; a subset of
- graphical.target). However it is at the discretion of
+ graphical.target). However, it is at the discretion of
the administrator to configure it as an alias to any
other target unit. See
systemd.special7
@@ -425,7 +425,7 @@
individual Linux control groups named after the unit
which they belong to in the private systemd
hierarchy. (see cgroups.txt
+ url="https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt">cgroups.txt
for more information about control groups, or short
"cgroups"). systemd uses this to effectively keep
track of processes. Control group information is
@@ -473,14 +473,14 @@
Systemd contains native implementations of
various tasks that need to be executed as part of the
- boot process. For example, it sets the host name or
+ boot process. For example, it sets the hostname or
configures the loopback network device. It also sets
up and mounts various API file systems, such as
/sys or
/proc.For more information about the concepts and
- ideas behind systemd please refer to the Original
Design Document.
@@ -535,7 +535,9 @@
disable commands of
the
systemctl1
- tool.
+ tool. Full list of directories is provided in
+ systemd.unit5.
+
@@ -564,7 +566,9 @@
tool can handle both global (i.e. for
all users) and private (for one user)
enabling/disabling of
- units.
+ units. Full list of directories is provided in
+ systemd.unit5.
+
@@ -607,7 +611,7 @@
- SIGTERM
+ SIGTERMUpon receiving this
signal the systemd system manager
@@ -627,7 +631,7 @@
- SIGINT
+ SIGINTUpon receiving this
signal the systemd system manager will
@@ -639,11 +643,11 @@
systemd user managers
treat this signal the same way as
- SIGTERM.
+ SIGTERM.
- SIGWINCH
+ SIGWINCHWhen this signal is
received the systemd system manager
@@ -659,7 +663,7 @@
- SIGPWR
+ SIGPWRWhen this signal is
received the systemd manager
@@ -671,7 +675,7 @@
- SIGUSR1
+ SIGUSR1When this signal is
received the systemd manager will try
@@ -680,7 +684,7 @@
- SIGUSR2
+ SIGUSR2When this signal is
received the systemd manager will log
@@ -691,7 +695,7 @@
- SIGHUP
+ SIGHUPReloads the complete
daemon configuration. This is mostly
@@ -700,7 +704,7 @@
- SIGRTMIN+0
+ SIGRTMIN+0Enters default mode, starts the
default.target
@@ -710,7 +714,7 @@
- SIGRTMIN+1
+ SIGRTMIN+1Enters rescue mode,
starts the
@@ -721,7 +725,7 @@
- SIGRTMIN+2
+ SIGRTMIN+2Enters emergency mode,
starts the
@@ -732,7 +736,7 @@
- SIGRTMIN+3
+ SIGRTMIN+3Halts the machine,
starts the
@@ -743,7 +747,7 @@
- SIGRTMIN+4
+ SIGRTMIN+4Powers off the machine,
starts the
@@ -754,7 +758,7 @@
- SIGRTMIN+5
+ SIGRTMIN+5Reboots the machine,
starts the
@@ -765,7 +769,7 @@
- SIGRTMIN+6
+ SIGRTMIN+6Reboots the machine via kexec,
starts the
@@ -776,31 +780,31 @@
- SIGRTMIN+13
+ SIGRTMIN+13Immediately halts the machine.
- SIGRTMIN+14
+ SIGRTMIN+14Immediately powers off the machine.
- SIGRTMIN+15
+ SIGRTMIN+15Immediately reboots the machine.
- SIGRTMIN+16
+ SIGRTMIN+16Immediately reboots the machine with kexec.
- SIGRTMIN+20
+ SIGRTMIN+20Enables display of
status messages on the console, as
@@ -811,7 +815,7 @@
- SIGRTMIN+21
+ SIGRTMIN+21Disables display of
status messages on the console, as
@@ -822,23 +826,23 @@
- SIGRTMIN+22
- SIGRTMIN+23
+ SIGRTMIN+22
+ SIGRTMIN+23Sets the log level to
debug
(or info on
- SIGRTMIN+23), as
+ SIGRTMIN+23), as
controlled via
systemd.log_level=debug
(or systemd.log_level=info
- on SIGRTMIN+23) on
+ on SIGRTMIN+23) on
the kernel command
line.
- SIGRTMIN+24
+ SIGRTMIN+24Immediately exits the
manager (only available for --user
@@ -846,28 +850,28 @@
- SIGRTMIN+26
- SIGRTMIN+27
- SIGRTMIN+28
- SIGRTMIN+29
+ SIGRTMIN+26
+ SIGRTMIN+27
+ SIGRTMIN+28
+ SIGRTMIN+29Sets the log level to
journal-or-kmsg
(or console on
- SIGRTMIN+27,
+ SIGRTMIN+27,
kmsg on
- SIGRTMIN+28,
+ SIGRTMIN+28,
or syslog-or-kmsg
- on SIGRTMIN+29), as
+ on SIGRTMIN+29), as
controlled via
systemd.log_target=journal-or-kmsg
(or systemd.log_target=console
- on SIGRTMIN+27,
+ on SIGRTMIN+27,
systemd.log_target=kmsg
- on SIGRTMIN+28,
+ on SIGRTMIN+28,
or
systemd.log_target=syslog-or-kmsg
- on SIGRTMIN+29) on
+ on SIGRTMIN+29) on
the kernel command
line.
@@ -987,7 +991,7 @@
/proc/cmdline
instead.:
-
+ systemd.unit=rd.systemd.unit=
@@ -1004,7 +1008,7 @@
option prefixed with
rd. is honored
only in the initial RAM disk (initrd),
- while the one that isn't prefixed only
+ while the one that is not prefixed only
in the main system.
@@ -1012,9 +1016,9 @@
systemd.dump_core=Takes a boolean
- argument. If
+ argument. If ,
systemd dumps core when it
- crashes. Otherwise no core dump is
+ crashes. Otherwise, no core dump is
created. Defaults to
.
@@ -1023,9 +1027,9 @@
systemd.crash_shell=Takes a boolean
- argument. If
+ argument. If ,
systemd spawns a shell when it
- crashes. Otherwise no shell is
+ crashes. Otherwise, no shell is
spawned. Defaults to
, for security
reasons, as the shell is not protected
@@ -1040,14 +1044,14 @@
argument. If positive systemd
activates the specified virtual
terminal when it crashes. Defaults to
- -1.
+ -1.
systemd.confirm_spawn=Takes a boolean
- argument. If
+ argument. If ,
asks for confirmation when spawning
processes. Defaults to
.
@@ -1057,7 +1061,7 @@
systemd.show_status=Takes a boolean
- argument. If
+ argument. If ,
shows terse service status updates on
the console during bootup. Defaults to
, unless
@@ -1095,34 +1099,43 @@
systemd.setenv=Takes a string
- argument in the form
- VARIABLE=VALUE. May be used to set
- environment variables for the init
- process and all its children at boot
- time. May be used more than once to
- set multiple variables. If the equal
- sign and variable are missing it unsets
- an environment variable which might be
- passed in from the initial ram
- disk.
+ argument in the form VARIABLE=VALUE.
+ May be used to set default environment
+ variables to add to forked child processes.
+ May be used more than once to set multiple
+ variables.quiet
- If passed turns off
+ Turn off
status output at boot, much like
systemd.show_status=false
would. Note that this option is also
read by the kernel itself and disables
- kernel log output to the
- kernel. Passing this option hence
- turns off the usual output from both
- the system manager and the
+ kernel log output. Passing this option
+ hence turns off the usual output from
+ both the system manager and the kernel.
+
+
+
+
+ debug
+
+ Turn on debugging
+ output. This is equivalent to
+ systemd.log_level=debug.
+ Note that this option is also read by
+ the kernel itself and enables kernel
+ debug output. Passing this option
+ hence turns on the debug output from
+ both the system manager and the
kernel.
+ -bemergencyBoot into emergency
@@ -1206,7 +1219,7 @@
Daemon status
notification socket. This is an
- AF_UNIX datagram socket and is used to
+ AF_UNIX datagram socket and is used to
implement the daemon notification
logic as implemented by
sd_notify3.
@@ -1219,7 +1232,7 @@
Used internally by the
shutdown8
tool to implement delayed
- shutdowns. This is an AF_UNIX datagram
+ shutdowns. This is an AF_UNIX datagram
socket.
@@ -1230,7 +1243,7 @@
communication channel between
systemctl1
and the systemd process. This is an
- AF_UNIX stream socket. This interface
+ AF_UNIX stream socket. This interface
is private to systemd and should not
be used in external
projects.
@@ -1254,7 +1267,8 @@
See Also
- systemd.conf5,
+ The systemd Homepage,
+ systemd-system.conf5,
locale.conf5,
systemctl1,
journalctl1,
@@ -1265,7 +1279,8 @@
systemd.special5,
pkg-config1,
kernel-command-line7,
- bootup7
+ bootup7,
+ systemd.directives7