X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml;h=f590b3fa1111b9c458d69f875bc7fa7d3c91472d;hb=ed942a9eb22d50f667909ad6184b45015d28d054;hp=b77b60d92048801f615593bae642ad71255cbaeb;hpb=e06e62f4a1d7a976587c4241eca157ce98d2da33;p=elogind.git
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index b77b60d92..f590b3fa1 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -52,6 +52,7 @@
bluetooth.target,
ctrl-alt-del.target,
cryptsetup.target,
+ cryptsetup-pre.target,
dbus.service,
dbus.socket,
default.target,
@@ -71,6 +72,8 @@
local-fs-pre.target,
multi-user.target,
network.target,
+ network-online.target,
+ network-pre.target,
nss-lookup.target,
nss-user-lookup.target,
paths.target,
@@ -79,7 +82,6 @@
reboot.target,
remote-fs.target,
remote-fs-pre.target,
- remote-fs-setup.target,
rescue.target,
initrd-root-fs.target,
rpcbind.target,
@@ -100,7 +102,11 @@
system-update.target,
time-sync.target,
timers.target,
- umount.target
+ umount.target,
+ -.slice,
+ system.slice,
+ user.slice,
+ machine.slice
@@ -314,7 +320,7 @@
dependencies of type
Before= to
sysroot-usr.mount
- and all mount points fround in
+ and all mount points found in
/etc/fstab
that have the
and
@@ -381,34 +387,72 @@
this unit during
installation. This is best
configured via
- WantedBy=multi-uer.target
+ WantedBy=multi-user.target
in the unit's
[Install]
section.
- network.target
+ network-online.target
- systemd automatically
- adds dependencies of type
- After= for
- this target unit to all SysV
- init script service units with
- an LSB header referring to the
- $network
- facility.
+ Units that strictly
+ require a configured network
+ connection should pull in
+ network-online.target
+ (via a
+ Wants= type
+ dependency) and order
+ themselves after it. This
+ target unit is intended to
+ pull in a service that delays
+ further execution until the
+ network is sufficiently set
+ up. What precisely this
+ requires is left to the
+ implementation of the network
+ managing service.
- This unit is supposed to
- indicate when the network is
- "up", but it is only very
- loosely defined what that is
- supposed to mean. Also see Note the distinction
+ between this unit and
+ network.target. This
+ unit is an active unit
+ (i.e. pulled in by the
+ consumer rather than the
+ provider of this
+ functionality) and pulls in a
+ service which possibly adds
+ substantial delays to further
+ execution. In contrast,
+ network.target
+ is a passive unit (i.e. pulled
+ in by the provider of the
+ functionality, rather than the
+ consumer) that usually does
+ not delay execution
+ much. Usually,
+ network.target
+ is part of the boot of most
+ systems, while
+ network-online.target
+ is not, except when at least
+ one unit requires it. Also see
+ Running
Services After the Network is
up for more
information.
-
+
+ All mount units for
+ remote network file systems
+ automatically pull in this
+ unit, and order themselves
+ after it. Note that networking
+ daemons that simply provide
+ functionality to other hosts
+ generally do not need to pull
+ this in.
+
paths.target
@@ -481,29 +525,6 @@
facility.
-
- remote-fs-setup.target
-
- This target unit is
- automatically pulled in (by a
- Wants= type
- dependency) by all remote
- mount points. It can be used
- to run certain units when at
- least one remote file system
- is to be mounted. Note that
- this target is not ordered
- against the remote mounts, use
- remote-fs-pre.target
- for that (see below).
-
- Again, this target unit
- is not
- suitable for ordering, it is
- only useful for pulling in
- other units.
-
- rescue.target
@@ -769,7 +790,7 @@
available at boot.
This may be used to pull
- in printer management
+ in smartcard management
daemons dynamically when
smartcard hardware is
found.
@@ -786,7 +807,7 @@
This may be used to pull
in audio management daemons
- dynamically when printer
+ dynamically when audio
hardware is found.
@@ -801,7 +822,7 @@
services. These targets are generally not part of the
initial boot transaction, unless they are explicitly
pulled in by one of the implementing services. Note
- specifically, that these passive
+ specifically that these passive
target units are generally not pulled in by the
consumer of a service, but by the provider of the
service. This means: a consuming service should order
@@ -811,7 +832,36 @@
(via a Wants= type
dependency).
+ Note that these passive units cannot be started
+ manually, i.e. systemctl start
+ time-sync.target will fail with an
+ error. They can only be pulled in by dependency. This
+ is enforced since they exist for ordering purposes
+ only and thus are not useful as only unit within a
+ transaction.
+
+
+ cryptsetup-pre.target
+
+ This passive target unit
+ may be pulled in by services
+ that want to run before any
+ encrypted block device is set
+ up. All encrypted block
+ devices are set up after this
+ target has been reached. Since
+ the shutdown order is
+ implicitly the reverse
+ start-up order between units,
+ this target is particularly
+ useful to ensure that a
+ service is shut down only
+ after all encrypted block
+ devices are fully
+ stopped.
+
+ local-fs-pre.target
@@ -824,6 +874,59 @@
all local mounts.
+
+ network.target
+
+ This unit is supposed to
+ indicate when network
+ functionality is available,
+ but it is only very weakly
+ defined what that is supposed
+ to mean, with one exception:
+ at shutdown, a unit that is
+ ordered after
+ network.target
+ will be stopped before the
+ network -- to whatever level
+ it might be set up then -- is
+ shut down. It is hence useful
+ when writing service files
+ that require network access on
+ shutdown, which should order
+ themselves after this target,
+ but not pull it in. Also see
+ Running
+ Services After the Network is
+ up for more
+ information. Also see
+ network-online.target
+ described above.
+
+ systemd automatically
+ adds dependencies of type
+ After= for
+ this target unit to all SysV
+ init script service units with
+ an LSB header referring to the
+ $network
+ facility.
+
+
+
+ network-pre.target
+
+ This passive target unit
+ may be pulled in by services
+ that want to run before any
+ network is set up, for example
+ for the purpose of setting up a
+ firewall. All network
+ management software orders
+ itself after this target, but
+ does not pull it in.
+
+ nss-lookup.target
@@ -835,7 +938,12 @@
user/group name lookups for
which
nss-user-lookup.target
- should be used. systemd
+ should be used. All services
+ for which the availability of
+ full host/network name
+ resolution is essential should
+ be ordered after this target,
+ but not pull it in. systemd
automatically adds
dependencies of type
After= for
@@ -857,7 +965,16 @@
host/network name lookups for
which
nss-lookup.target
- should be used.
+ should be used. All services
+ for which the availability of
+ the full user/group database is
+ essential should be ordered
+ after this target, but not
+ pull it in. Note that system
+ users are always resolvable,
+ and hence do not require any
+ special ordering against this
+ target.
@@ -878,23 +995,22 @@
Wants= type
dependency. If the unit wants
to be pulled in by the first
- remote mount showing up it
+ remote mount showing up, it
should use
- remote-fs-setup.target
+ network-online.target
(see above).
-
- Again, this target unit
- is not
- suitable for pulling in other
- units, it is only useful for
- ordering.rpcbind.target
- systemd automatically
- adds dependencies of type
+ The portmapper/rpcbind
+ pulls in this target and
+ orders itself before it, to
+ indicate its
+ availability. systemd
+ automatically adds
+ dependencies of type
After= for
this target unit to all SysV
init script service units with
@@ -906,14 +1022,24 @@
time-sync.target
- systemd automatically
- adds dependencies of type
+ Services responsible for
+ synchronizing the system clock
+ from a remote source (such as
+ NTP client implementations)
+ should pull in this target and
+ order themselves before
+ it. All services where correct
+ time is essential should be
+ ordered after this unit, but
+ not pull it in. systemd
+ automatically adds
+ dependencies of type
After= for
this target unit to all SysV
init script service units with
an LSB header referring to the
$time
- facility.
+ facility.
@@ -935,7 +1061,7 @@
smartcard.target,
sound.target.
- In addition the following special unit is
+ In addition, the following special unit is
understood only when systemd runs as service instance:
@@ -950,8 +1076,8 @@
terminate the user service
manager should start this
unit. If systemd receives
- SIGTERM or SIGINT when running
- as user service daemon it will
+ SIGTERM or SIGINT when running
+ as user service daemon, it will
start this unit.Normally, this pulls in
@@ -965,6 +1091,63 @@
+
+ Special Slice Units
+
+ There are four .slice units
+ which form the basis of the hierarchy for assignment
+ of resources for services, users, and virtual machines
+ or containers.
+
+
+
+ -.slice
+
+ The root slice is the
+ root of the hierarchy. It
+ usually does not contain units
+ directly, but may be used to
+ set defaults for the whole
+ tree.
+
+
+
+
+ system.slice
+
+ By default, all services
+ services started by
+ systemd are
+ found in this slice.
+
+
+
+
+ user.slice
+
+ By default, all user
+ processes and services started
+ on behalf of the user,
+ including the per-user systemd
+ instance are found in this
+ slice.
+
+
+
+
+ machine.slice
+
+ By default, all virtual
+ machines and containers
+ registered with
+ systemd-machined
+ are found in this slice.
+
+
+
+
+
+
See Also
@@ -973,6 +1156,7 @@
systemd.service5,
systemd.socket5,
systemd.target5,
+ systemd.slice5,
bootup7,
systemd-fstab-generator8