mirror of
https://github.com/systemd/systemd.git
synced 2024-12-23 21:35:11 +03:00
ff12a7954c
As in2a5fcfae02and in3e67e5c992using /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.
38 lines
1.2 KiB
Bash
Executable File
38 lines
1.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
set -ex
|
|
set -o pipefail
|
|
|
|
# Let's run this test only if the "memory.oom.group" cgroupfs attribute
|
|
# exists. This test is a bit too strict, since the "memory.events"/"oom_kill"
|
|
# logic has been around since a longer time than "memory.oom.group", but it's
|
|
# an easier thing to test for, and also: let's not get confused by older
|
|
# kernels where the concept was still new.
|
|
|
|
if test -f /sys/fs/cgroup/system.slice/testsuite.service/memory.oom.group ; then
|
|
|
|
systemd-analyze log-level debug
|
|
systemd-analyze log-target console
|
|
|
|
# Run a service that is guaranteed to be the first candidate for OOM killing
|
|
systemd-run --unit=oomtest.service -p Type=exec -p OOMScoreAdjust=1000 -p OOMPolicy=stop -p MemoryAccounting=yes /bin/sleep infinity
|
|
|
|
# Trigger an OOM killer run
|
|
echo 1 > /proc/sys/kernel/sysrq
|
|
echo f > /proc/sysrq-trigger
|
|
|
|
while : ; do
|
|
STATE=`systemctl show -p ActiveState --value oomtest.service`
|
|
[ "$STATE" = "failed" ] && break
|
|
sleep .5
|
|
done
|
|
|
|
RESULT=`systemctl show -p Result --value oomtest.service`
|
|
test "$RESULT" = "oom-kill"
|
|
|
|
systemd-analyze log-level info
|
|
fi
|
|
|
|
echo OK > /testok
|
|
|
|
exit 0
|