2020-03-04 12:35:06 +03:00
#!/usr/bin/env bash
2021-10-17 19:13:06 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
2021-04-09 20:39:41 +03:00
set -eux
2018-01-05 14:20:22 +03:00
set -o pipefail
2023-05-10 21:17:19 +03:00
# Test changing the main PID
2023-05-16 23:41:03 +03:00
# shellcheck source=test/units/util.sh
. " $( dirname " $0 " ) " /util.sh
2019-04-03 09:19:08 +03:00
systemd-analyze log-level debug
2018-01-05 14:20:22 +03:00
2023-05-10 21:17:19 +03:00
# The main service PID should be the parent bash process
MAINPID = " ${ PPID : ? } "
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
# Start a test process inside of our own cgroup
sleep infinity &
INTERNALPID = $!
disown
# Start a test process outside of our own cgroup
2023-03-31 19:42:38 +03:00
systemd-run -p DynamicUser = 1 --unit= test-sleep.service /bin/sleep infinity
EXTERNALPID = " $( systemctl show -P MainPID test-sleep.service) "
2018-01-05 14:20:22 +03:00
# Update our own main PID to the external test PID, this should work
2021-04-09 20:54:42 +03:00
systemd-notify MAINPID = " $EXTERNALPID "
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $EXTERNALPID "
2018-01-05 14:20:22 +03:00
# Update our own main PID to the internal test PID, this should work, too
systemd-notify MAINPID = $INTERNALPID
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $INTERNALPID "
2018-01-05 14:20:22 +03:00
# Update it back to our own PID, this should also work
2023-05-10 21:17:19 +03:00
systemd-notify MAINPID = " $MAINPID "
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
# Try to set it to PID 1, which it should ignore, because that's the manager
systemd-notify MAINPID = 1
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
# Try to set it to PID 0, which is invalid and should be ignored
systemd-notify MAINPID = 0
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
# Try to set it to a valid but non-existing PID, which should be ignored. (Note
# that we set the PID to a value well above any known /proc/sys/kernel/pid_max,
# which means we can be pretty sure it doesn't exist by coincidence)
systemd-notify MAINPID = 1073741824
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
2019-04-27 03:22:40 +03:00
# Change it again to the external PID, without privileges this time. This should be ignored, because the PID is from outside of our cgroup and we lack privileges.
2021-04-09 20:54:42 +03:00
systemd-notify --uid= 1000 MAINPID = " $EXTERNALPID "
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
2019-04-27 03:22:40 +03:00
# Change it again to the internal PID, without privileges this time. This should work, as the process is on our cgroup, and that's enough even if we lack privileges.
2021-04-09 20:54:42 +03:00
systemd-notify --uid= 1000 MAINPID = " $INTERNALPID "
2023-05-10 21:17:19 +03:00
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $INTERNALPID "
2018-01-05 14:20:22 +03:00
# Update it back to our own PID, this should also work
2023-05-10 21:17:19 +03:00
systemd-notify --uid= 1000 MAINPID = " $MAINPID "
test " $( systemctl show -P MainPID testsuite-07.service) " -eq " $MAINPID "
2018-01-05 14:20:22 +03:00
2023-05-10 21:17:19 +03:00
cat >/tmp/test-mainpid.sh <<\E OF
2020-03-04 12:35:06 +03:00
#!/usr/bin/env bash
2018-01-05 14:20:22 +03:00
set -eux
set -o pipefail
# Create a number of children, and make one the main one
sleep infinity &
disown
sleep infinity &
2023-05-10 21:17:19 +03:00
MAINPID = $!
2018-01-05 14:20:22 +03:00
disown
sleep infinity &
disown
2023-05-10 21:17:19 +03:00
echo $MAINPID >/run/mainpidsh/pid
2018-01-05 14:20:22 +03:00
EOF
2023-03-31 19:42:38 +03:00
chmod +x /tmp/test-mainpid.sh
2018-01-05 14:20:22 +03:00
2023-05-10 21:17:19 +03:00
systemd-run --unit= test-mainpidsh.service \
-p StandardOutput = tty \
-p StandardError = tty \
-p Type = forking \
-p RuntimeDirectory = mainpidsh \
-p PIDFile = /run/mainpidsh/pid \
/tmp/test-mainpid.sh
2023-03-31 19:42:38 +03:00
test " $( systemctl show -P MainPID test-mainpidsh.service) " -eq " $( cat /run/mainpidsh/pid) "
2018-01-05 14:20:22 +03:00
2023-05-10 21:17:19 +03:00
cat >/tmp/test-mainpid2.sh <<\E OF
2020-03-04 12:35:06 +03:00
#!/usr/bin/env bash
2018-01-05 14:20:22 +03:00
set -eux
set -o pipefail
# Create a number of children, and make one the main one
sleep infinity &
disown
sleep infinity &
2023-05-10 21:17:19 +03:00
MAINPID = $!
2018-01-05 14:20:22 +03:00
disown
sleep infinity &
disown
2023-05-10 21:17:19 +03:00
echo $MAINPID >/run/mainpidsh2/pid
2018-01-05 14:20:22 +03:00
chown 1001:1001 /run/mainpidsh2/pid
EOF
2023-03-31 19:42:38 +03:00
chmod +x /tmp/test-mainpid2.sh
2018-01-05 14:20:22 +03:00
2023-05-10 21:17:19 +03:00
systemd-run --unit= test-mainpidsh2.service \
-p StandardOutput = tty \
-p StandardError = tty \
-p Type = forking \
-p RuntimeDirectory = mainpidsh2 \
-p PIDFile = /run/mainpidsh2/pid \
/tmp/test-mainpid2.sh
2023-03-31 19:42:38 +03:00
test " $( systemctl show -P MainPID test-mainpidsh2.service) " -eq " $( cat /run/mainpidsh2/pid) "
2018-01-05 14:20:22 +03:00
2023-03-31 19:42:38 +03:00
cat >/dev/shm/test-mainpid3.sh <<EOF
2020-03-04 12:35:06 +03:00
#!/usr/bin/env bash
2018-01-05 14:20:22 +03:00
set -eux
set -o pipefail
sleep infinity &
disown
sleep infinity &
disown
sleep infinity &
disown
# Let's try to play games, and link up a privileged PID file
ln -s ../mainpidsh/pid /run/mainpidsh3/pid
# Quick assertion that the link isn't dead
test -f /run/mainpidsh3/pid
EOF
2023-03-31 19:42:38 +03:00
chmod 755 /dev/shm/test-mainpid3.sh
2018-01-05 14:20:22 +03:00
2021-04-08 02:27:33 +03:00
# This has to fail, as we shouldn't accept the dangerous PID file, and then
# inotify-wait on it to be corrected which we never do.
2023-04-05 16:50:42 +03:00
( ! systemd-run \
--unit= test-mainpidsh3.service \
-p StandardOutput = tty \
-p StandardError = tty \
-p Type = forking \
-p RuntimeDirectory = mainpidsh3 \
-p PIDFile = /run/mainpidsh3/pid \
-p DynamicUser = 1 \
2023-05-10 21:17:19 +03:00
` # Make sanitizers happy when DynamicUser=1 pulls in instrumented systemd NSS modules` \
-p EnvironmentFile = -/usr/lib/systemd/systemd-asan-env \
2023-04-05 16:50:42 +03:00
-p TimeoutStartSec = 2s \
/dev/shm/test-mainpid3.sh)
2018-01-05 14:20:22 +03:00
# Test that this failed due to timeout, and not some other error
2023-03-31 19:42:38 +03:00
test " $( systemctl show -P Result test-mainpidsh3.service) " = timeout
2018-01-05 14:20:22 +03:00
2021-11-12 00:25:40 +03:00
# Test that scope units work
2023-03-31 19:42:38 +03:00
systemd-run --scope --unit test-true.scope /bin/true
test " $( systemctl show -P Result test-true.scope) " = success
2021-11-12 00:25:40 +03:00
# Test that user scope units work as well
systemctl start user@4711.service
2023-03-31 19:42:38 +03:00
runas testuser systemd-run --scope --user --unit test-true.scope /bin/true
test " $( systemctl show -P Result test-true.scope) " = success
2021-11-12 00:25:40 +03:00
2019-04-03 09:19:08 +03:00
systemd-analyze log-level info