From: Lennart Poettering Date: Thu, 14 May 2020 17:24:08 +0000 (+0200) Subject: man: document the two new condition types X-Git-Tag: v246-rc1~356^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=410abf8304453c62b1ae61da757d6c079200d118;p=thirdparty%2Fsystemd.git man: document the two new condition types --- diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index b451c530206..b91c1ad0ecc 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1226,6 +1226,24 @@ + + ConditionEnvironment= + + ConditionEnvironment= may be used to check whether a specific + environment variable is set (or if prefixed with the exclamation mark — unset) in the service + manager's environment block. + + The argument may be a single word, to check if the variable with this name is defined in the + environment block, or an assignment + (name=value), to check if + the variable with this exact value is defined. Note that the environment block of the service + manager itself is checked, i.e. not any variables defined with Environment= or + EnvironmentFile=, as described above. This is particularly useful when the + service manager runs inside a containerized environment or as per-user service manager, in order to + check for variables passed in by the enclosing container manager or PAM. + + + ConditionSecurity= @@ -1346,6 +1364,18 @@ + + ConditionPathIsEncrypted= + + ConditionPathIsEncrypted= is similar to + ConditionPathExists= but verifies that the underlying file system's backing + block device is encrypted using dm-crypt/LUKS. Note that this check does not cover ext4 + per-directory encryption, and only detects block level encryption. Moreover, if the specified path + resides on a file system on top of a loopback block device, only encryption above the loopback device is + detected. It is not detected whether the file system backing the loopback block device is encrypted. + + + ConditionDirectoryNotEmpty=