summaryrefslogtreecommitdiff
path: root/test/test-execute/exec-passenvironment-absent.service
diff options
context:
space:
mode:
authorFilipe Brandenburger <filbranden@google.com>2015-11-08 10:37:05 -0800
committerFilipe Brandenburger <filbranden@google.com>2015-11-11 07:55:23 -0800
commit4c80d201ace0377312c27143afab04e9c9f1ee64 (patch)
tree1d17a615d8278d640961a11a9c8eb06bcb5fe77d /test/test-execute/exec-passenvironment-absent.service
parent4ad4beec7f927d1d592d85bba6af2f7ba106ad8b (diff)
downloadsystemd-4c80d201ace0377312c27143afab04e9c9f1ee64.tar.gz
test-execute: Add tests for new PassEnvironment= directive
Check the base case, plus erasing the list, listing the same variable name more than once and when variables are absent from the manager execution environment. Confirmed that `sudo ./test-execute` passes and that modifying the test cases (or the values of the set variables in test-execute.c) is enough to make the test cases fail.
Diffstat (limited to 'test/test-execute/exec-passenvironment-absent.service')
-rw-r--r--test/test-execute/exec-passenvironment-absent.service7
1 files changed, 7 insertions, 0 deletions
diff --git a/test/test-execute/exec-passenvironment-absent.service b/test/test-execute/exec-passenvironment-absent.service
new file mode 100644
index 0000000000..7d5e32a4eb
--- /dev/null
+++ b/test/test-execute/exec-passenvironment-absent.service
@@ -0,0 +1,7 @@
+[Unit]
+Description=Test for PassEnvironment with variables absent from the execution environment
+
+[Service]
+ExecStart=/bin/sh -x -c 'test "$${VAR1-unset}" = "unset" && test "$${VAR2-unset}" = "unset" && test "$${VAR3-unset}" = "unset"'
+Type=oneshot
+PassEnvironment=VAR1 VAR2 VAR3