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

#!/usr/bin/env bash
set -x
set -e
set -o pipefail

echo 1 >/sys/fs/selinux/enforce || {
    echo "Can't make selinux enforcing, skipping test"
    touch /testok
    exit
}

runcon -t systemd_test_start_t systemctl start hola
runcon -t systemd_test_reload_t systemctl reload hola
runcon -t systemd_test_stop_t systemctl stop hola

touch /testok
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 09:35:06 +00:00			`#!/usr/bin/env bash`
tests: add test-selinux-checks 2016-01-31 09:01:43 +00:00			`set -x`
			`set -e`
			`set -o pipefail`

test/TEST-06: skip test if no selinux I put SELINUX=disabled on my laptop, and the test fails with ENOENT when trying to write to /sys/fs/selinux/enforce. It's a bit of a special case, but let's avoid the failure. 2020-03-19 16:57:50 +01:00			`echo 1 >/sys/fs/selinux/enforce \|\| {`
			`echo "Can't make selinux enforcing, skipping test"`
			`touch /testok`
			`exit`
			`}`

tests: add test-selinux-checks 2016-01-31 09:01:43 +00:00			`runcon -t systemd_test_start_t systemctl start hola`
			`runcon -t systemd_test_reload_t systemctl reload hola`
			`runcon -t systemd_test_stop_t systemctl stop hola`

			`touch /testok`