From 69bdb3b1500d8889c9fbea823d1e5511531d400e Mon Sep 17 00:00:00 2001 From: Mark Stosberg Date: Thu, 3 Oct 2019 16:26:42 -0400 Subject: [PATCH] man: document updated newline support Since v239 newlines have been allowed for PassEnvironment= and EnvironmentFile=, due to #8471. This PR documents the behavior change. --- man/systemd.exec.xml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 6dcccc3..2f6fc0b 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -1869,6 +1869,12 @@ SystemCallErrorNumber=EPERM variable definitions. The parser strips leading and trailing whitespace from the values of assignments, unless you use double quotes ("). + C escapes + are supported, but not + most control characters. + \t and \n can be used to insert tabs and newlines within + EnvironmentFile=. + The argument passed should be an absolute filename or wildcard expression, optionally prefixed with -, which indicates that if the file does not exist, it will not be read and no error or warning message is logged. This option may be specified more than once in which case all specified files are @@ -1899,6 +1905,12 @@ SystemCallErrorNumber=EPERM Variables set for invoked processes due to this setting are subject to being overridden by those configured with Environment= or EnvironmentFile=. + C escapes + are supported, but not + most control characters. + \t and \n can be used to insert tabs and newlines within + EnvironmentFile=. + Example: PassEnvironment=VAR1 VAR2 VAR3 passes three variables VAR1, -- 2.7.4