Red Hat Bugzilla – Bug 144882
Arping utility hangs if SIGALRM blocked
Last modified: 2007-11-30 17:07:05 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Texas Instruments; .NET CLR 1.1.4322) Description of problem: If "arping" utility is forked (using system() library function) from a parent process in which SIGALRM signal is blocked then the system() function call never returns. The problem is that arping utility installs a SIGALRM handler but does not bother to unblock it - so its logic does not work if it inherited blocked SIGALRM. Version-Release number of selected component (if applicable): iputils-20020927-11 How reproducible: Always Steps to Reproduce: 1.Block SIGALRM signal 2.Call srping utility ising system() library function 3.Observe that system() function never returns Actual Results: The process hangs forever Expected Results: The process should have exited Additional info:
Created attachment 109666 [details] C file to reproduce the bug
This comes from your test C code. I see what you mean with SIGALRM locked but it works on my machine. # ./mytest1 Executing command [arping -c 1 -I eth0 192.168.1.1] ARPING 192.168.1.1 from 192.168.1.13 eth0 Unicast reply from 192.168.1.1 [00:10:4B:6B:18:87] 5.317ms Sent 1 probes (1 broadcast(s)) Received 1 response(s) System call returned with status 0 # rpm -q iputils iputils-20020927-19 (includes updated ifenslave, might fix the issue)
retested, problem not found