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.
16 lines
468 B
Bash
Executable file
16 lines
468 B
Bash
Executable file
#!/usr/bin/env bash
|
|
set -x
|
|
set -e
|
|
set -o pipefail
|
|
|
|
[[ "$(systemctl show -p DefaultLimitNOFILESoft)" = "DefaultLimitNOFILESoft=10000" ]]
|
|
[[ "$(systemctl show -p DefaultLimitNOFILE)" = "DefaultLimitNOFILE=16384" ]]
|
|
|
|
[[ "$(systemctl show -p LimitNOFILESoft testsuite.service)" = "LimitNOFILESoft=10000" ]]
|
|
[[ "$(systemctl show -p LimitNOFILE testsuite.service)" = "LimitNOFILE=16384" ]]
|
|
|
|
[[ "$(ulimit -n -S)" = "10000" ]]
|
|
[[ "$(ulimit -n -H)" = "16384" ]]
|
|
|
|
touch /testok
|