From ccc162e03c9608b53577bc2155111891ed6fc012 Mon Sep 17 00:00:00 2001 From: Simon Schricker Date: Mon, 13 May 2019 10:47:43 +0200 Subject: [PATCH] man: mention garbage collection of failed conditions See discussion: https://github.com/systemd/systemd/issues/2234 --- man/systemd.unit.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 AssertArchitecture=, AssertVirtualization=, … 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. + (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. ConditionArchitecture= may be used to check whether the system is running on a specific