X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=32bca0b607bd00f34e6a6ad8221d7016d1ebd43c;hb=405e0255d5e6950180d9563f1a26294b5360db03;hp=dc89ee7eab43d8222c47cf3939ab9a8ea920aee8;hpb=9ba0bc4e0f3cc606635547c6215f5af8982851df;p=elogind.git
diff --git a/man/systemd.xml b/man/systemd.xml
index dc89ee7ea..32bca0b60 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.
@@ -144,11 +144,13 @@
- Tell systemd to run a
- system instance (resp. user
- instance), even if the process ID is
- not 1 (resp. is 1), i.e. systemd is
- not (resp. is) run as init process.
+ For ,
+ tell systemd to run a
+ system instance, even if the process ID is
+ not 1, i.e. systemd is not run as init process.
+ does the opposite,
+ running a user instance even if the process
+ ID is 1.
Normally it should not be necessary to
pass these options, as systemd
automatically detects the mode it is
@@ -251,11 +253,11 @@
Sets the default
- output resp. error output for all
- services and sockets, i.e. controls
+ output or error output for all
+ services and sockets, respectively. That is, controls
the default for
- resp.
+ and
(see
systemd.exec5
for details). Takes one of
@@ -283,25 +285,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
@@ -310,7 +314,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.
@@ -367,6 +371,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
+ hierachial 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
@@ -423,7 +439,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
@@ -471,7 +487,7 @@
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
@@ -495,12 +511,12 @@
Specification.Systems which invoke systemd in a container
- resp. initrd environment should implement the
+ or initrd environment should implement the
Container
- Interface resp. or initrd
- Interface specifications.
+ Interface specifications, respectively.
@@ -533,7 +549,9 @@
disable commands of
the
systemctl1
- tool.
+ tool. Full list of directories is provided in
+ systemd.unit5.
+
@@ -562,7 +580,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.
+
@@ -605,7 +625,7 @@
- SIGTERM
+ SIGTERMUpon receiving this
signal the systemd system manager
@@ -625,7 +645,7 @@
- SIGINT
+ SIGINTUpon receiving this
signal the systemd system manager will
@@ -637,11 +657,11 @@
systemd user managers
treat this signal the same way as
- SIGTERM.
+ SIGTERM.
- SIGWINCH
+ SIGWINCHWhen this signal is
received the systemd system manager
@@ -657,7 +677,7 @@
- SIGPWR
+ SIGPWRWhen this signal is
received the systemd manager
@@ -669,7 +689,7 @@
- SIGUSR1
+ SIGUSR1When this signal is
received the systemd manager will try
@@ -678,7 +698,7 @@
- SIGUSR2
+ SIGUSR2When this signal is
received the systemd manager will log
@@ -689,7 +709,7 @@
- SIGHUP
+ SIGHUPReloads the complete
daemon configuration. This is mostly
@@ -698,7 +718,7 @@
- SIGRTMIN+0
+ SIGRTMIN+0Enters default mode, starts the
default.target
@@ -708,7 +728,7 @@
- SIGRTMIN+1
+ SIGRTMIN+1Enters rescue mode,
starts the
@@ -719,7 +739,7 @@
- SIGRTMIN+2
+ SIGRTMIN+2Enters emergency mode,
starts the
@@ -730,7 +750,7 @@
- SIGRTMIN+3
+ SIGRTMIN+3Halts the machine,
starts the
@@ -741,7 +761,7 @@
- SIGRTMIN+4
+ SIGRTMIN+4Powers off the machine,
starts the
@@ -752,7 +772,7 @@
- SIGRTMIN+5
+ SIGRTMIN+5Reboots the machine,
starts the
@@ -763,7 +783,7 @@
- SIGRTMIN+6
+ SIGRTMIN+6Reboots the machine via kexec,
starts the
@@ -774,31 +794,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
@@ -809,7 +829,7 @@
- SIGRTMIN+21
+ SIGRTMIN+21Disables display of
status messages on the console, as
@@ -820,44 +840,52 @@
- SIGRTMIN+22
- SIGRTMIN+23
+ SIGRTMIN+22
+ SIGRTMIN+23Sets the log level to
debug
- (resp. info on
- SIGRTMIN+23), as
+ (or info on
+ SIGRTMIN+23), as
controlled via
systemd.log_level=debug
- (resp. systemd.log_level=info
- on SIGRTMIN+23) on
+ (or systemd.log_level=info
+ on SIGRTMIN+23) on
the kernel command
line.
- SIGRTMIN+26
- SIGRTMIN+27
- SIGRTMIN+28
- SIGRTMIN+29
+ SIGRTMIN+24
+
+ Immediately exits the
+ manager (only available for --user
+ instances).
+
+
+
+ SIGRTMIN+26
+ SIGRTMIN+27
+ SIGRTMIN+28
+ SIGRTMIN+29Sets the log level to
journal-or-kmsg
- (resp. console on
- SIGRTMIN+27;
- resp. kmsg on
- SIGRTMIN+28;
- resp. syslog-or-kmsg
- on SIGRTMIN+29), as
+ (or console on
+ SIGRTMIN+27,
+ kmsg on
+ SIGRTMIN+28,
+ or syslog-or-kmsg
+ on SIGRTMIN+29), as
controlled via
systemd.log_target=journal-or-kmsg
- (resp. systemd.log_target=console
- on SIGRTMIN+27;
- resp. systemd.log_target=kmsg
- on SIGRTMIN+28;
- resp
+ (or systemd.log_target=console
+ on SIGRTMIN+27,
+ systemd.log_target=kmsg
+ on SIGRTMIN+28,
+ or
systemd.log_target=syslog-or-kmsg
- on SIGRTMIN+29) on
+ on SIGRTMIN+29) on
the kernel command
line.
@@ -867,7 +895,7 @@
Environment
-
+ $SYSTEMD_LOG_LEVELsystemd reads the
@@ -977,7 +1005,7 @@
/proc/cmdline
instead.:
-
+ systemd.unit=rd.systemd.unit=
@@ -992,7 +1020,7 @@
systemd.special7
for details about these units. The
option prefixed with
- rd. is honoured
+ rd. is honored
only in the initial RAM disk (initrd),
while the one that isn't prefixed only
in the main system.
@@ -1030,7 +1058,7 @@
argument. If positive systemd
activates the specified virtual
terminal when it crashes. Defaults to
- -1.
+ -1.
@@ -1073,42 +1101,50 @@
systemd.default_standard_output=systemd.default_standard_error=Controls default
- standard output/error output for
+ standard output and error output for
services, with the same effect as the
- resp.
+ and
command line arguments described
- above.
+ above, respectively.
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 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.
@@ -1143,12 +1179,12 @@
5Boot into the
- specified legacy SysV runlevel. This
- is equivalent to
+ specified legacy SysV runlevel. These
+ are equivalent to
systemd.unit=runlevel2.target,
systemd.unit=runlevel3.target,
systemd.unit=runlevel4.target,
- resp. systemd.unit=runlevel5.target
+ and systemd.unit=runlevel5.target, respectively,
and provided for compatibility reasons
and to be easier to
type.
@@ -1196,7 +1232,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.
@@ -1209,7 +1245,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.
@@ -1220,7 +1256,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.
@@ -1244,10 +1280,10 @@
See Also
- systemd.conf5,
+ systemd-system.conf5,
locale.conf5,
systemctl1,
- systemadm1,
+ journalctl1,
systemd-notify1,
daemon7,
sd-daemon3,
@@ -1255,7 +1291,8 @@
systemd.special5,
pkg-config1,
kernel-command-line7,
- bootup7
+ bootup7,
+ systemd.directives7