From 90a2ec10f2d43a8530aae856013518eb567c4039 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 6 Nov 2014 13:59:41 +0100 Subject: [PATCH] man: don't document ConditionNull=/AssertNull= as the are not particularly useful and simply confusing --- man/systemd.unit.xml | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 5d6f6eb14..dddcf09e3 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -950,7 +950,11 @@ ConditionDirectoryNotEmpty= ConditionFileNotEmpty= ConditionFileIsExecutable= - ConditionNull= + + Before starting a unit verify that the specified condition is @@ -1230,15 +1234,6 @@ exists, is a regular file and marked executable. - Finally, - ConditionNull= may - be used to add a constant condition - check value to the unit. It takes a - boolean argument. If set to - false, the condition - will always fail, otherwise - succeed. - If multiple conditions are specified, the unit will be executed if all of them apply (i.e. a logical AND @@ -1283,7 +1278,6 @@ AssertDirectoryNotEmpty= AssertFileNotEmpty= AssertFileIsExecutable= - AssertNull= Similar to the ConditionArchitecture=, -- 2.30.2