mirror of
https://github.com/systemd/systemd.git
synced 2024-10-27 10:25:37 +03:00
man/systemd-service: clarify env variable expansion
This clarifies some more aspects of `${FOO}` expansions in service units, mostly trying to answer my own doubts about what happens when the matching variable is not defined.
This commit is contained in:
parent
f3a604e4cf
commit
3db1c62d22
@ -1106,10 +1106,10 @@
|
|||||||
|
|
||||||
<para>Basic environment variable substitution is supported. Use
|
<para>Basic environment variable substitution is supported. Use
|
||||||
<literal>${FOO}</literal> as part of a word, or as a word of its
|
<literal>${FOO}</literal> as part of a word, or as a word of its
|
||||||
own, on the command line, in which case it will be replaced by the
|
own, on the command line, in which case it will be erased and replaced
|
||||||
value of the environment variable including all whitespace it
|
by the exact value of the environment variable (if any) including all
|
||||||
contains, resulting in a single argument. Use
|
whitespace it contains, always resulting in exactly a single argument.
|
||||||
<literal>$FOO</literal> as a separate word on the command line, in
|
Use <literal>$FOO</literal> as a separate word on the command line, in
|
||||||
which case it will be replaced by the value of the environment
|
which case it will be replaced by the value of the environment
|
||||||
variable split at whitespace, resulting in zero or more arguments.
|
variable split at whitespace, resulting in zero or more arguments.
|
||||||
For this type of expansion, quotes are respected when splitting
|
For this type of expansion, quotes are respected when splitting
|
||||||
|
Loading…
Reference in New Issue
Block a user