X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.special.xml;h=8ccccc2798713a4b0f6a7d1d9fdee0781d320ce0;hp=4d0660714531f45d3227de3a5e258fdb0d6e45f8;hb=03ee5c38cb0da193dd08733fb4c0c2809cee6a99;hpb=6b4991cfde6c0a0b62e836ca75ae362779c474d4 diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 4d0660714..8ccccc279 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -820,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 @@ -939,7 +939,7 @@ 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). @@ -996,7 +996,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 +1012,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