X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.xml;h=10ce375dae7f31232099bc9686b6b80960370eb9;hb=a53692f7b4fb0af771bd510436cc592ef2919f86;hp=ef95641387568f227febef3e97ba3ec1347ac144;hpb=74d005783e355acc784d123024e33bbb66ef9ef1;p=elogind.git
diff --git a/man/systemd.xml b/man/systemd.xml
index ef9564138..10ce375da 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -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,7 +473,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
@@ -643,7 +643,7 @@
systemd user managers
treat this signal the same way as
- SIGTERM.
+ SIGTERM.
@@ -1008,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.
@@ -1016,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
.
@@ -1027,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
@@ -1051,7 +1051,7 @@
systemd.confirm_spawn=Takes a boolean
- argument. If
+ argument. If ,
asks for confirmation when spawning
processes. Defaults to
.
@@ -1061,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
@@ -1099,16 +1099,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 +1135,7 @@
+ -bemergencyBoot into emergency
@@ -1271,6 +1267,7 @@
See Also
+ The systemd Homepage,
systemd-system.conf5,
locale.conf5,
systemctl1,