systemd-stable/test/test-execute/exec-environmentfile.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for EnvironmentFile

[Service]
ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$VAR4" = "new\nline" && test "$$VAR5" = passwordwithbackslashes'
Type=oneshot
EnvironmentFile=/tmp/test-exec_environmentfile.conf
tests: add spdx license header to test unit/link/network/conf files Those are all consumed by our parser, so they all support comments. I was considering whether they should have a license header at all, but in the end I decided to add it because those files are often created by copying parts of real unit files. And if the real ones have a license, then those might as well. It's easier to add it than to make an exception. 2021-10-17 18:07:22 +02:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test-execute: add test for EnvironmentFile 2015-10-30 16:55:44 +01:00			`[Unit]`
			`Description=Test for EnvironmentFile`

			`[Service]`
test: add testcase for environment file variables with backslashes systemd silently strips out backslashes in variables from environment files. Add a testcase that explicitly tests for this behaviour. 2018-05-10 15:28:10 +02:00			`ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$VAR4" = "new\nline" && test "$$VAR5" = passwordwithbackslashes'`
test-execute: add test for EnvironmentFile 2015-10-30 16:55:44 +01:00			`Type=oneshot`
			`EnvironmentFile=/tmp/test-exec_environmentfile.conf`