Difference between revisions of "EMI gLExec release test plan and report"

@@ Line 337: / Line 337: @@
 REPRODUCE: run glexec and flood it with signals after a very small delay, such that it traps signals e.g. during a syslog call. E.g. run several times:
- #!/bin/bash
+<pre>
- export GLEXEC_CLIENT_CERT=/tmp/x509up_u`id -u`
+#!/bin/bash
- export X509_USER_PROXY=/tmp/x509up_u`id -u`
+export GLEXEC_CLIENT_CERT=/tmp/x509up_u`id -u`
- /usr/sbin/glexec /usr/bin/id -a &
+export X509_USER_PROXY=/tmp/x509up_u`id -u`
- pid=$!
+/usr/sbin/glexec /usr/bin/id -a &
- ps -fp $pid
+pid=$!
- for ((i=1; i<100; i++));do
+ps -fp $pid
-	s=$((i%64+1))
+for ((i=1; i<100; i++));do
-	((s==9 || s==19 || s==32 || s==33)) && s=11
+       s=$((i%64+1))
-	kill -$s $pid
+       ((s==9 || s==19 || s==32 || s==33)) && s=11
- done
+       kill -$s $pid
+done
+</pre>
 CHECK: gLExec does not hang up, even after many times.

Revision as of 13:36, 14 May 2012