tests: don't check the current ipcs limits

The ipcs/limit test checks the current kernel limits, but we have no
clue about the current setting, so on on 64bit system it may overflow.

It's better to test for well known limits only. For the random setting
is there ipcs/limit2 test.

Signed-off-by: Karel Zak <kzak@redhat.com>
This commit is contained in:
Karel Zak 2014-12-19 13:36:07 +01:00
parent 4d9a1969f7
commit 7ef338f39d
3 changed files with 8 additions and 12 deletions

View File

@ -1,11 +1,7 @@
load original values
maximalize kernel setting
check for difference between kernel and IPC
/proc/sys/kernel/shmmni OK
/proc/sys/kernel/shmall OK
/proc/sys/kernel/shmmax OK
maximalize kernel setting
re-check for difference between kernel and IPC
/proc/sys/kernel/shmmni OK
/proc/sys/kernel/shmall OK
/proc/sys/kernel/shmmax OK
write original values to kernel

View File

@ -64,14 +64,17 @@ IPCS_IDX=$(seq 0 $(( ${#IPCS_PROCFILES[*]} - 1 )))
# checker
function ipcs_limits_check {
for i in $IPCS_IDX; do
echo -n ${IPCS_PROCFILES[$i]}
a=$(eval ${IPCS_KERNEL_CMD[$i]})
b=$(eval ${IPCS_CMD[$i]})
#echo -n " RAW: "
#cat ${IPCS_PROCFILES[$i]}
#echo "CMD: ${ICPS_KERNEL_CMD[$i]}"
#echo
#echo "KERNEL-CMD: ${IPCS_KERNEL_CMD[$i]}"
#echo "KERNEL-RAW: $(cat ${IPCS_PROCFILES[$i]})"
#echo "IPCS-CMD: ${IPCS_CMD[$i]}"
#echo
if [ x"$a" == x"$b" ]; then
echo " OK"

View File

@ -35,15 +35,12 @@ for i in $IPCS_IDX; do
SHM_ORG[$i]=$(cat ${IPCS_PROCFILES[$i]})
done >> $TS_OUTPUT
ts_log "check for difference between kernel and IPC"
ipcs_limits_check >> $TS_OUTPUT
ts_log "maximalize kernel setting"
for i in $IPCS_IDX; do
echo ${IPCS_LIMITS[$i]} >> ${IPCS_PROCFILES[$i]}
done >> $TS_OUTPUT
ts_log "re-check for difference between kernel and IPC"
ts_log "check for difference between kernel and IPC"
ipcs_limits_check >> $TS_OUTPUT
ts_log "write original values to kernel"