X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.special.xml;h=f84639e2b4829d0ed6805289ecd47f7a30f10cd9;hp=7dbc5580e26e20d620004dd8bbe96184d177ad8d;hb=ee43f49b7889b546fe05a141459d7f1ddf129bd4;hpb=fade1ec6e05f9f6c3718be622e259d2c8e61508c diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 7dbc5580e..f84639e2b 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, @@ -72,6 +73,7 @@ multi-user.target, network.target, network-online.target, + network-pre.target, nss-lookup.target, nss-user-lookup.target, paths.target, @@ -320,11 +322,10 @@ sysroot-usr.mount and all mount points found in /etc/fstab - that have the - and + that have - mount options set. - + and not have + mount options set. @@ -385,7 +386,7 @@ this unit during installation. This is best configured via - WantedBy=multi-uer.target + WantedBy=multi-user.target in the unit's [Install] section. @@ -448,7 +449,7 @@ after it. Note that networking daemons that simply provide functionality to other hosts - generally don't need to pull + generally do not need to pull this in. @@ -820,7 +821,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 @@ -839,6 +840,27 @@ 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 @@ -866,7 +888,13 @@ will be stopped before the network -- to whatever level it might be set up then -- is - shut down. Also see Running Services After the Network is up for more @@ -882,7 +910,20 @@ 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. @@ -896,7 +937,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 @@ -918,7 +964,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. @@ -939,23 +994,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 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 @@ -967,14 +1021,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. @@ -996,7 +1060,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: @@ -1012,7 +1076,7 @@ manager should start this unit. If systemd receives SIGTERM or SIGINT when running - as user service daemon it will + as user service daemon, it will start this unit. Normally, this pulls in @@ -1039,40 +1103,44 @@ -.slice The root slice is the - root of the hierarchy. It does - not contain services directly, - but is used to set defaults - for the whole tree. + root of the hierarchy. It + usually does not contain units + directly, but may be used to + set defaults for the whole + tree. system.slice - This slice contains + By default, all services services started by - systemd. + systemd are + found in this slice. user.slice - This slice contains user + By default, all user processes and services started on behalf of the user, including the per-user systemd - instance. + instance are found in this + slice. machine.slice - This slice contains - virtual machines and - containers registered with - systemd-machined. + By default, all virtual + machines and containers + registered with + systemd-machined + are found in this slice.