diff options
author | Lennart Poettering <lennart@poettering.net> | 2010-08-09 22:32:30 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2010-08-09 22:32:30 +0200 |
commit | 69dd2852bb2c433b517d89792adb4461a4178aa1 (patch) | |
tree | f303fd9de62719c117a68c336bac5999ead3a3af /man/systemd.unit.xml | |
parent | 6e98720f14dc25ee1d43f951d5c4d79b04ad7506 (diff) |
manager: when two pending jobs conflict, keep the one that "conflicts", remove the one that is "conflicted"
This gives the writer of units control which unit is kept and which is
stopped when two units conflict.
Diffstat (limited to 'man/systemd.unit.xml')
-rw-r--r-- | man/systemd.unit.xml | 17 |
1 files changed, 16 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 585145ab37..e5d5968ab2 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -336,7 +336,22 @@ independent of and orthogonal to the <varname>After=</varname> and <varname>Before=</varname> ordering - dependencies.</para></listitem> + dependencies.</para> + + <para>If a unit A that conflicts with + a unit B is scheduled to be started at + the same time as B, the transaction + will either fail (in case both are + required part of the transaction) or + be modified to be fixed (in case one + or both jobs are not a required part + of the transaction). In the latter + case the job that is not the required + will be removed, or in case both are + not required the unit that conflicts + will be started and the unit that is + conflicted is + stopped.</para></listitem> </varlistentry> <varlistentry> |