Prev: How would I terminate just some foreground processes?
Next: Reading /proc/<pid>/maps
From: Jonathan de Boyne Pollard on 23 Jan 2010 13:23
>
>>>
>>> Isn't this a very common requirement ?
>>>
>> No. In fact, it seems fundamentally broken to me. Why do you think
>> you need/want to do this?
>>
> I can think of some scenarios. Imagine a case where the parent forks
> off a bunch of child processes to do some work, expecting to get the
> results back via return codes, pipes, or something else. If the
> parent dies for whatever reason, it would make sense to kill the child
> processes because any work they do won't be seen by anyone anymore.
>
.... which is the very raison d'�tre of SIGPIPE.

 | 
Pages: 1
Prev: How would I terminate just some foreground processes?
Next: Reading /proc/<pid>/maps