test/test-execute/exec-execsearchpath-environment.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Service]
ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$PATH" = "/tmp:/bin"'
Type=oneshot
ExecSearchPath=/tmp:/bin
Environment="VAR1=word1 word2" VAR2=word3 "VAR3=$word 5 6"
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`
core: Add ExecSearchPath parameter to specify the directory relative to which binaries executed by Exec= should be found Currently there does not exist a way to specify a path relative to which all binaries executed by Exec should be found. The only way is to specify the absolute path. This change implements the functionality to specify a path relative to which binaries executed by Exec= can be found. Closes #6308 2021-07-08 17:10:47 -07:00			`[Service]`
			`ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$PATH" = "/tmp:/bin"'`
			`Type=oneshot`
			`ExecSearchPath=/tmp:/bin`
			`Environment="VAR1=word1 word2" VAR2=word3 "VAR3=$word 5 6"`