systemd/test/test-execute/exec-dynamicuser-runtimedirectory1.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for RuntimeDirectory with RuntimeDirectoryPreserve=yes and DynamicUser=yes

[Service]
ExecStart=sh -x -c 'test -d %t/test-exec_runtimedirectorypreserve'
ExecStart=sh -x -c 'test "$$RUNTIME_DIRECTORY" = "%t/test-exec_runtimedirectorypreserve"'
ExecStart=sh -x -c 'touch $$RUNTIME_DIRECTORY/test'
Type=oneshot
RuntimeDirectory=test-exec_runtimedirectorypreserve
RuntimeDirectoryPreserve=yes
DynamicUser=yes
EnvironmentFile=-/usr/lib/systemd/systemd-asan-env
ReadWritePaths=-/coverage
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: add test cases for RuntimeDirectoryPreserve=yes 2019-10-02 00:22:58 +09:00			`[Unit]`
			`Description=Test for RuntimeDirectory with RuntimeDirectoryPreserve=yes and DynamicUser=yes`

			`[Service]`
tests: use relative paths in ExecStart= and friends We want to retain some of the full paths in order to test more code paths. But the default should be to use the command name only. This makes the tests less visually cluttered. 2024-01-04 15:24:52 +01:00			`ExecStart=sh -x -c 'test -d %t/test-exec_runtimedirectorypreserve'`
			`ExecStart=sh -x -c 'test "$$RUNTIME_DIRECTORY" = "%t/test-exec_runtimedirectorypreserve"'`
			`ExecStart=sh -x -c 'touch $$RUNTIME_DIRECTORY/test'`
test: add test cases for RuntimeDirectoryPreserve=yes 2019-10-02 00:22:58 +09:00			`Type=oneshot`
			`RuntimeDirectory=test-exec_runtimedirectorypreserve`
			`RuntimeDirectoryPreserve=yes`
			`DynamicUser=yes`
test-execute: Load systemd-asan-env environment file if available When DynamicUser= is enabled, we need LD_PRELOAD to be configured correctly as the tests will load systemd's nss module which will complain when built with sanitizers if the sanitizer libraries were not loaded first. 2024-05-27 13:34:40 +02:00			`EnvironmentFile=-/usr/lib/systemd/systemd-asan-env`
test-execute: Make /coverage writable in DynamicUser= tests DynamicUser=yes implies ProtectSystem=yes, so let's explicitly make sure the coverage directory is writable in these tests. 2024-12-03 14:45:43 +01:00			`ReadWritePaths=-/coverage`