Hi all, while working on another bug, I discovered the "strange" way systemd is parsing Environment= in .service and thought it was worth documenting (because I don't expect people to find this syntax by themselves unless they read the parsing code ;)
-- Frederic Crozat <[email protected]> SUSE
>From 2cfd1ed4d853be4a22cc102037347c9041bf5ced Mon Sep 17 00:00:00 2001 From: Frederic Crozat <[email protected]> Date: Thu, 24 Jan 2013 17:55:42 +0100 Subject: [PATCH] man: systemd.exec - explicit Environment assignment Be more verbose about using space in Environment field and not using value of other variables Fixes https://bugzilla.redhat.com/show_bug.cgi?id=840260 --- man/systemd.exec.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 8a22ac0..70859fd 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -286,7 +286,14 @@ empty string is assigned to this option the list of environment variables is reset, all prior - assignments have no effect. See + assignments have no effect. + Value of other environment variable will + not be expanded when used as value. + If you need to assign value containing space + to a variable, use double quotes (") + for the assignment. Example: <literal> + Environment="VARIABLE1=word1 word2"</literal>. + See <citerefentry><refentrytitle>environ</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details.</para></listitem> </varlistentry> -- 1.7.10.4
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
