shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-24 21:34:08 +03:00
Code

man: reword description of triggering conditions

Browse Source 
Fixes #13758.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2019-10-29 14:54:36 +01:00
parent 337b733449
commit 54166ceece
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man/systemd.unit.xml
View File

@ -1022,13 +1022,13 @@
</para>
<para>If multiple conditions are specified, the unit will be executed if all of them apply (i.e. a
logical AND is applied). Condition checks can be prefixed with a pipe symbol (<literal>|</literal>) in
which case a condition becomes a triggering condition. If at least one triggering condition is defined
for a unit, then the unit will be executed if at least one of the triggering conditions apply and all
of the non-triggering conditions. If you prefix an argument with the pipe symbol and an exclamation
mark, the pipe symbol must be passed first, the exclamation second. If any of these options is assigned
the empty string, the list of conditions is reset completely, all previous condition settings (of any
kind) will have no effect.</para>
logical AND is applied). Condition checks can use a pipe symbol (<literal>|</literal>) after the equals
sign (<literal>Condition…=|…</literal>), which causes the condition becomes a triggering condition. If
at least one triggering condition is defined for a unit, then the unit will be executed if at least one
of the triggering conditions apply and all of the non-triggering conditions. If you prefix an argument
with the pipe symbol and an exclamation mark, the pipe symbol must be passed first, the exclamation
second. If any of these options is assigned the empty string, the list of conditions is reset
completely, all previous condition settings (of any kind) will have no effect.</para>
<para>The <varname>AssertArchitecture=</varname>, <varname>AssertVirtualization=</varname>, … options
provide a similar mechanism that causes the job to fail (instead of being skipped). The failed check is