diff options
| author | Simon Schricker <sschricker@suse.de> | 2019-05-13 10:47:43 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2019-05-13 15:34:49 +0200 |
| commit | ccc162e03c9608b53577bc2155111891ed6fc012 (patch) | |
| tree | 6b1120750247ae0e5c2b56bd91deed7e1f1db104 /man/systemd.unit.xml | |
| parent | Merge pull request #12546 from jwrdegoede/hwdb-logitech-s510 (diff) | |
| download | systemd-ccc162e03c9608b53577bc2155111891ed6fc012.tar.xz systemd-ccc162e03c9608b53577bc2155111891ed6fc012.zip | |
man: mention garbage collection of failed conditions
See discussion:
https://github.com/systemd/systemd/issues/2234
Diffstat (limited to '')
| -rw-r--r-- | man/systemd.unit.xml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 4b283880c3..84af5109b8 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1020,7 +1020,9 @@ or runtime environment doesn't require their functionality. Use the various <varname>AssertArchitecture=</varname>, <varname>AssertVirtualization=</varname>, … options for a similar mechanism that causes the job to fail (instead of being skipped) and results in logging about the failed check - (instead of being silently processed). For details about assertion conditions see below.</para> + (instead of being silently processed). For details about assertion conditions see below. Units with failed + conditions are considered to be in a clean state and will be garbage collected if they are not referenced. + This means, that when queried, the condition failure may or may not show up in the state of the unit.</para> <para><varname>ConditionArchitecture=</varname> may be used to check whether the system is running on a specific |