X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml;h=38b94a7657ed49a86c4390f7f4734e714f285467;hb=06c17c39a8345deef1ecff4dd5ef262f968c9be2;hp=4588f5899901d2740f91c0f1a039eefb1118eef0;hpb=5e9dfd2ef99bad1000a6246a160c096c4dbd2158;p=elogind.git diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 4588f5899..38b94a765 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -100,7 +100,11 @@ system-update.target, time-sync.target, timers.target, - umount.target + umount.target, + -.slice, + system.slice, + user.slice, + machine.slice @@ -381,7 +385,7 @@ this unit during installation. This is best configured via - WantedBy=multi-uer.target + WantedBy=multi-user.target in the unit's [Install] section. @@ -444,7 +448,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. @@ -816,7 +820,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 @@ -862,7 +866,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 @@ -878,7 +888,6 @@ an LSB header referring to the $network facility. - @@ -892,7 +901,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 @@ -914,7 +928,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. @@ -935,23 +958,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 @@ -963,14 +985,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. @@ -992,7 +1024,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: @@ -1007,8 +1039,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 @@ -1022,6 +1054,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 defalt, all virtual + machines and containers + registered with + systemd-machined + are found in this slice. + + + + + + See Also @@ -1030,6 +1119,7 @@ systemd.service5, systemd.socket5, systemd.target5, + systemd.slice5, bootup7, systemd-fstab-generator8