Re: system() does not wait

[bluto]

Is script1 getting signaled (i.e. is the shell's value for ($? & 127) for script1 a non-zero value)? If so, what is the value? system() blocks SIGINT and SIGQUIT, but it's possible another signal is hitting it. I've seen wierd cases where a child spawned a vendor's utility that stupidly signaled the process group (e.g. something like SIGHUP). The child was ready and caught the signal, but the parent was blissfully ignorant of what signals might indirectly be thrown (and died). If this is the case, one way to get around this is to ignore the signal in the parent during the system() call...

{
    local $SIG{'HUP'} = 'IGNORE';  # put your signal here
    system(...);
}

You may get away with just ignoring all of the signals, but that depends on your code.

[cbolcato]

The following line of code were executed immediately after the system() and produced the out put below: #CODE $exit_value = $? >> 8; $signal_num = $? & 127; $dumped_core = $? & 128; print "$?\n"; print "$exit_value\n"; print "$signal_num\n"; print "$dumped_core\n";

[cbolcato]

sorry the following is the output: #OUTPUT -1 16777215 127 128

[fizbin]

If $? is -1, then script2 is not getting invoked. How do you know that script2 is getting invoked at all? Is it doing something? Can you see it in a ps statement?

Please print out an error message that contains the string-ified version of $! (That is, put something like print "$!" in your code).

I strongly suspect that either you're forgetting to set your PATH variable or have forgotten to make SCRIPT2 executeable. Or maybe you typo'ed the name of SCRIPT2 in your system statement.

Either way, the complete and total lack of markup in your responses makes it exceedingly difficult to read what you're trying to say.