X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=bcbfa02ba1fcc9a94cc12309994c4c5153c61cb2;hb=1e2fd62d70ff1a960551d28fce745847a9dbd3b7;hp=b4b4845305544fb77264afe7c6c6521e62f936b3;hpb=05cc726731c5cec952722f1c14acb08e3d4d5e98;p=elogind.git
diff --git a/man/systemd.xml b/man/systemd.xml
index b4b484530..bcbfa02ba 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -21,7 +21,8 @@
along with systemd; If not, see .
-->
-
+systemd
@@ -88,19 +89,6 @@
The following options are understood:
-
-
-
-
- Prints a short help
- text and exits.
-
-
-
-
- Prints a systemd version
- identifier and exits.
-
@@ -118,25 +106,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.
@@ -217,7 +191,7 @@
Set log level. As
argument this accepts a numerical log
- level or the well-known syslog3
+ level or the well-known syslog3
symbolic names (lowercase):
,
,
@@ -233,7 +207,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
.
@@ -278,6 +252,9 @@
to
.
+
+
+
@@ -285,25 +262,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 +291,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 +348,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
@@ -393,7 +384,7 @@
and ordering dependencies are placed between two
units. Also note that the majority of dependencies are
implicitly created and maintained by systemd. In most
- cases it should be unnecessary to declare additional
+ cases, it should be unnecessary to declare additional
dependencies manually, however it is possible to do
this.
@@ -415,7 +406,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 +416,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
@@ -433,7 +424,7 @@
file system hierarchy (beneath
/sys/fs/cgroup/systemd/), or in tools
such as
- ps1
+ ps1
(ps xawf -eo pid,user,cgroup,args
is particularly useful to list all processes and the
systemd units they belong to.).
@@ -480,7 +471,7 @@
/proc.
For more information about the concepts and
- ideas behind systemd please refer to the Original
Design Document.
@@ -1008,7 +999,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.
@@ -1016,9 +1007,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
.
@@ -1027,9 +1018,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
@@ -1051,7 +1042,7 @@
systemd.confirm_spawn=Takes a boolean
- argument. If
+ argument. If ,
asks for confirmation when spawning
processes. Defaults to
.
@@ -1061,14 +1052,20 @@
systemd.show_status=Takes a boolean
- argument. If
- shows terse service status updates on
- the console during bootup. Defaults to
+ argument or the constant
+ auto. If
+ , shows terse
+ service status updates on the console
+ during bootup.
+ auto behaves like
+ until a service
+ fails or there is a significant delay
+ in boot. Defaults to
, unless
is passed as
kernel command line option in which
case it defaults to
- .
+ auto.
@@ -1099,16 +1096,11 @@
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.
@@ -1140,6 +1132,7 @@
+ -bemergencyBoot into emergency
@@ -1271,6 +1264,7 @@
See Also
+ The systemd Homepage,
systemd-system.conf5,
locale.conf5,
systemctl1,
@@ -1280,9 +1274,9 @@
sd-daemon3,
systemd.unit5,
systemd.special5,
- pkg-config1,
+ pkg-config1,
kernel-command-line7,
- bootup7,
+ bootup7,
systemd.directives7