Re: Signal to parent-process. Does it affect it's children?

I think the problem is that waitpid does not continue after the signal has been processed, however the child process is still running. I suggest putting a loop around waitpid. The return value of waitpid should give you a hint if the child actually exited or if a signal has interrupted the call.

Update: By the way, I don't think that you need to set the signal handler again in status. Once it has been set, it gets executed every time a USR1 signal arrives.

Comment on Re: Signal to parent-process. Does it affect it's children? Download Code

Replies are listed 'Best First'.
Re^2: Signal to parent-process. Does it affect it's children? by rapide (Beadle) on Sep 07, 2008 at 18:42 UTC
Seems like the interruption terminated the child. So far I haven't seen anything in the Poddoc manual. Resetting the signal handler depends on the system and whether its safe system calls or not. I'd rather be safe if I'm porting it to another system ..	[reply]
Re^3: Signal to parent-process. Does it affect it's children? by tilly (Archbishop) on Sep 09, 2008 at 21:45 UTC
If you're ever thinking of porting to a Windows system, you should expect everything involving forking and external signals to break. That's because on the platform Perl emulates forking with multithreading, and that emulation may not work well with whatever emulation you find of Unix signals.	[reply]