systemd-stable/test/units/testsuite-23.sh

#!/usr/bin/env bash
set -ex
set -o pipefail

systemd-analyze log-level debug
systemd-analyze log-target console

# Create a binary for which execve() will fail
touch /tmp/brokenbinary
chmod +x /tmp/brokenbinary

# These three commands should succeed.
systemd-run --unit=one -p Type=simple /bin/sleep infinity
systemd-run --unit=two -p Type=simple -p User=idontexist /bin/sleep infinity
systemd-run --unit=three -p Type=simple /tmp/brokenbinary

# And now, do the same with Type=exec, where the latter two should fail
systemd-run --unit=four -p Type=exec /bin/sleep infinity
! systemd-run --unit=five -p Type=exec -p User=idontexist /bin/sleep infinity
! systemd-run --unit=six -p Type=exec /tmp/brokenbinary

systemd-run --unit=seven -p KillSignal=SIGTERM -p RestartKillSignal=SIGINT -p Type=exec /bin/sleep infinity
# Both TERM and SIGINT happen to have the same number on all architectures
test $(systemctl show --value -p KillSignal seven.service) -eq 15
test $(systemctl show --value -p RestartKillSignal seven.service) -eq 2

systemctl restart seven.service
systemctl stop seven.service

systemd-analyze log-level info

echo OK > /testok

exit 0
treewide: more portable bash shebangs As in 2a5fcfae024ffc370bb780572279f45a1da3f946 and in 3e67e5c9928f8b1e1c5a63def88d53ed1fed12eb using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability. 2020-03-04 12:35:06 +03:00			`#!/usr/bin/env bash`
test: add test for Type=exec 2018-07-17 13:35:12 +03:00			`set -ex`
			`set -o pipefail`

test: use newer verb to set log levels 2019-04-03 09:19:08 +03:00			`systemd-analyze log-level debug`
			`systemd-analyze log-target console`
test: add test for Type=exec 2018-07-17 13:35:12 +03:00
			`# Create a binary for which execve() will fail`
			`touch /tmp/brokenbinary`
			`chmod +x /tmp/brokenbinary`

			`# These three commands should succeed.`
			`systemd-run --unit=one -p Type=simple /bin/sleep infinity`
			`systemd-run --unit=two -p Type=simple -p User=idontexist /bin/sleep infinity`
			`systemd-run --unit=three -p Type=simple /tmp/brokenbinary`

			`# And now, do the same with Type=exec, where the latter two should fail`
			`systemd-run --unit=four -p Type=exec /bin/sleep infinity`
			`! systemd-run --unit=five -p Type=exec -p User=idontexist /bin/sleep infinity`
			`! systemd-run --unit=six -p Type=exec /tmp/brokenbinary`

core: add support for RestartKillSignal= to override signal used for restart jobs v2: - if RestartKillSignal= is not specified, fall back to KillSignal=. This is necessary to preserve backwards compatibility (and keep KillSignal= generally useful). 2019-10-01 16:15:06 +03:00			`systemd-run --unit=seven -p KillSignal=SIGTERM -p RestartKillSignal=SIGINT -p Type=exec /bin/sleep infinity`
			`# Both TERM and SIGINT happen to have the same number on all architectures`
			`test $(systemctl show --value -p KillSignal seven.service) -eq 15`
			`test $(systemctl show --value -p RestartKillSignal seven.service) -eq 2`

			`systemctl restart seven.service`
			`systemctl stop seven.service`

test: use newer verb to set log levels 2019-04-03 09:19:08 +03:00			`systemd-analyze log-level info`
test: add test for Type=exec 2018-07-17 13:35:12 +03:00
			`echo OK > /testok`

			`exit 0`