From: Zbigniew Jędrzejewski-Szmek Date: Wed, 6 Nov 2019 12:42:13 +0000 (+0100) Subject: man: describe ordering in case of Conflicts= X-Git-Tag: v244-rc1~83^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F13962%2Fhead;p=thirdparty%2Fsystemd.git man: describe ordering in case of Conflicts= Fixes #13421. --- diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 1670992feda..96907d7a2f5 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -671,13 +671,16 @@ Conflicts= - A space-separated list of unit names. - Configures negative requirement dependencies. If a unit has a - Conflicts= setting on another unit, - starting the former will stop the latter and vice versa. Note - that this setting is independent of and orthogonal to the - After= and Before= - ordering dependencies. + A space-separated list of unit names. Configures negative requirement + dependencies. If a unit has a Conflicts= setting on another unit, starting the + former will stop the latter and vice versa. + + Note that this setting does not imply an ordering dependency, similarly to the + Wants= and Requires= dependencies described above. This means + that to ensure that the conflicting unit is stopped before the other unit is started, an + After= or Before= dependency must be declared. It doesn't + matter which of the two ordering dependencies is used, because stop jobs are always ordered before + start jobs, see the discussion in Before=/After= below. If unit A that conflicts with unit B is scheduled to be started at the same time as B, the transaction will either