Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: How to optionally kill a child, and capture status if not killed.

by sgifford (Prior)
on Apr 25, 2008 at 20:30 UTC ( #682908=note: print w/replies, xml ) Need Help??

in reply to How to optionally kill a child, and capture status if not killed.

For the status, are you looking for just the exit status you get from wait? If so, have the monitor process read the exit status from the child process, then just call exit to exit with the same status. Things get a bit more complicated if you want to keep all of the information returned by wait, such as whether the process was killed by the signal and whether it dumped core, but often you don't.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://682908]
[ambrus]: MLX: if it's a work email, then it's probably not Uncle Sam that matters, but what the account managing server at work thinks your name is. Those can differ. For example, we've had two co-workers with identical real name at one point,
[ambrus]: so one got a stupid suffix in the email account (people have email address based on their real name here usually).

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (11)
As of 2017-01-19 14:09 GMT
Find Nodes?
    Voting Booth?
    Do you watch meteor showers?

    Results (170 votes). Check out past polls.