[SOLVED] Signal Blocking by the exec() command
Posted: Thu Aug 18, 2005 10:43 am
Howdy Folks,
First time post so go easy!
Has anyone experienced signal blocking problems with the exec() command?
I'm testing exec() with the vmstat command on HP-UX unix. The same problem is occuring on Linux flavors (Red-hat and Suse) but I'm testing now on HP-UX.
If i run vmstat from the command line and follow it with a trace all works Ok. I pass it a SIGUSR1, it doesn't recognise it and bombs out.
Now if i call vmstat using the exec() function (i'm implementing a WebUI) and then pass it the SIGUSR1 from the command line, the signal never reaches the command, as outputted by the trace.
Why is this signal getting blocked? I've tried the same with the SIGALRM and that gets through.
Any ideas?
Many Thanks,
Ray
First time post so go easy!
Has anyone experienced signal blocking problems with the exec() command?
I'm testing exec() with the vmstat command on HP-UX unix. The same problem is occuring on Linux flavors (Red-hat and Suse) but I'm testing now on HP-UX.
If i run vmstat from the command line and follow it with a trace all works Ok. I pass it a SIGUSR1, it doesn't recognise it and bombs out.
Now if i call vmstat using the exec() function (i'm implementing a WebUI) and then pass it the SIGUSR1 from the command line, the signal never reaches the command, as outputted by the trace.
Why is this signal getting blocked? I've tried the same with the SIGALRM and that gets through.
Any ideas?
Many Thanks,
Ray