shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-26 14:04:03 +03:00
Code
systemd/test/test-execute/exec-dynamicuser-statedir.service

88 lines
2.7 KiB
SYSTEMD
Raw Normal View History

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 for DynamicUser= + StateDirectory= Also, tests for DynamicUser= should really run for system mode, as we allocate from a system resource. (This also increases the test timeout to 2min. If one of our tests really hangs then waiting for 2min longer doesn't hurt either. The old 2s is really short, given that we run in potentially slow VM environments for this test. This becomes noticable when the slow "find" command this adds is triggered)
2017-09-28 23:41:06 +02:00
[Unit]
Description=Test DynamicUser= with StateDirectory=
[Service]
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -w %S/waldo
ExecStart=test -w %S/quux/pief
ExecStart=test -w %S/aaa
ExecStart=test -w %S/aaa/bbb
ExecStart=test -w %S/aaa/ccc
ExecStart=test -w %S/xxx
ExecStart=test -w %S/xxx/yyy
ExecStart=test -w %S/xxx/zzz
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -w %S/abc
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -w %S/aaa/111
ExecStart=test -w %S/aaa/222
ExecStart=test -w %S/aaa/333
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -w %S/d:ef
test: add test for DynamicUser= + StateDirectory= Also, tests for DynamicUser= should really run for system mode, as we allocate from a system resource. (This also increases the test timeout to 2min. If one of our tests really hangs then waiting for 2min longer doesn't hurt either. The old 2s is really short, given that we run in potentially slow VM environments for this test. This becomes noticable when the slow "find" command this adds is triggered)
2017-09-28 23:41:06 +02:00
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -d %S/waldo
ExecStart=test -d %S/quux/pief
ExecStart=test -d %S/aaa
ExecStart=test -d %S/aaa/bbb
ExecStart=test -d %S/aaa/ccc
ExecStart=test -d %S/xxx
ExecStart=test -d %S/xxx/yyy
ExecStart=test -d %S/xxx/zzz
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -d %S/abc
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -L %S/aaa/111
ExecStart=test -L %S/aaa/222
ExecStart=test -L %S/aaa/333
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -L %S/d:ef
test: add more tests for StateDirectory= with DynamicUser= This also moves the check for writable paths from test-execute to TEST-34. Closes #10337.
2022-09-22 13:08:32 +09:00
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=touch %S/waldo/hoge
ExecStart=touch %S/quux/pief/hoge
ExecStart=touch %S/aaa/hoge
ExecStart=touch %S/aaa/bbb/hoge
ExecStart=touch %S/aaa/ccc/hoge
ExecStart=touch %S/xxx/hoge
ExecStart=touch %S/xxx/yyy/hoge
ExecStart=touch %S/xxx/zzz/hoge
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=touch %S/abc/hoge
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=touch %S/aaa/111/foo
ExecStart=touch %S/aaa/222/foo
ExecStart=touch %S/aaa/333/foo
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=touch %S/d:ef/foo
test: add more tests for StateDirectory= with DynamicUser= This also moves the check for writable paths from test-execute to TEST-34. Closes #10337.
2022-09-22 13:08:32 +09:00
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -f %S/waldo/hoge
ExecStart=test -f %S/quux/pief/hoge
ExecStart=test -f %S/aaa/hoge
ExecStart=test -f %S/aaa/bbb/hoge
ExecStart=test -f %S/aaa/ccc/hoge
ExecStart=test -f %S/xxx/hoge
ExecStart=test -f %S/xxx/yyy/hoge
ExecStart=test -f %S/xxx/zzz/hoge
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -f %S/abc/hoge
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -f %S/aaa/111/foo
ExecStart=test -f %S/aaa/222/foo
ExecStart=test -f %S/aaa/333/foo
ExecStart=test -f %S/xxx/foo
ExecStart=test -f %S/xxx/yyy/foo
ExecStart=test -f %S/xxx/zzz/foo
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -f %S/d:ef/foo
test: add more tests for StateDirectory= with DynamicUser= This also moves the check for writable paths from test-execute to TEST-34. Closes #10337.
2022-09-22 13:08:32 +09:00
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -f %S/private/waldo/hoge
ExecStart=test -f %S/private/quux/pief/hoge
ExecStart=test -f %S/private/aaa/hoge
ExecStart=test -f %S/private/aaa/bbb/hoge
ExecStart=test -f %S/private/aaa/ccc/hoge
ExecStart=test -f %S/private/xxx/hoge
ExecStart=test -f %S/private/xxx/yyy/hoge
ExecStart=test -f %S/private/xxx/zzz/hoge
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=test -f %S/private/abc/hoge
test-execute: drop capabilities when testing with user manager Before this, tests are split into two categories, system and user, but both are running in fully privileged environment. Hence, unprivileged user scope was mostly not covered by the test. Let's run all tests in both system and user scopes, and drop capabilities when Manager is running in user scope. This also makes the host environment protected more from the test run.
2023-02-03 12:28:31 +09:00
ExecStart=test -f %S/private/aaa/111/foo
ExecStart=test -f %S/private/aaa/222/foo
ExecStart=test -f %S/private/aaa/333/foo
ExecStart=test -f %S/private/xxx/foo
ExecStart=test -f %S/private/xxx/yyy/foo
ExecStart=test -f %S/private/xxx/zzz/foo
test: add more tests for StateDirectory= with DynamicUser= This also moves the check for writable paths from test-execute to TEST-34. Closes #10337.
2022-09-22 13:08:32 +09:00
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
ExecStart=sh -x -c 'test "$$STATE_DIRECTORY" = "%S/aaa:%S/aaa/bbb:%S/aaa/ccc:%S/abc:%S/quux/pief:%S/waldo:%S/xxx:%S/xxx/yyy:%S/xxx/zzz"'
test: add test for DynamicUser= + StateDirectory= Also, tests for DynamicUser= should really run for system mode, as we allocate from a system resource. (This also increases the test timeout to 2min. If one of our tests really hangs then waiting for 2min longer doesn't hurt either. The old 2s is really short, given that we run in potentially slow VM environments for this test. This becomes noticable when the slow "find" command this adds is triggered)
2017-09-28 23:41:06 +02:00
Type=oneshot
DynamicUser=yes
test-execute: add unit tests for *DirectorySymlink=
2023-06-02 23:00:18 +01:00
StateDirectory=waldo quux/pief aaa/bbb aaa aaa/ccc xxx/yyy:aaa/111 xxx:aaa/222 xxx/zzz:aaa/333 abc:d\:ef
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
Copy Permalink