[mpich-discuss] Process termination with Hydra
Pavan Balaji
balaji at mcs.anl.gov
Sun Mar 13 22:09:54 CDT 2011
FYI, I had to revert this addition (what you are calling "sub-process
termination") from Hydra as it was having some unexpected side-effects.
For now, Hydra will only cleanup the processes that it spawned. If you
fork other processes in your application, you will be responsible for
cleaning them up. You'll get SIGTERM and SIGKILL signals in your
application, which you can catch and use them to cleanup any child
processes you might have spawned.
-- Pavan
On 03/12/2011 12:24 AM, Pavan Balaji wrote:
>
> Nicolas just pointed out a part of your previous email about this:
>
> =======================================================================
> my application forks sub-processes. While I see that parent
> application process quits, but forked sub-processed are still left
> around. Another example is using valgrind (memcheck spawned process).
> I often see that sub-process are left around if I kill application in
> between. That makes me think that Hydra isn't cleaning sub-processes
> properly.
> =======================================================================
>
> I've added this support as well in r8222.
>
> -- Pavan
>
> On 03/11/2011 10:33 PM, Pavan Balaji wrote:
>>
>> On 03/11/2011 05:23 PM, Jain, Rohit wrote:
>>> Would it improve sub-process termination too?
>>
>> What is sub-process termination?
>>
>> -- Pavan
>>
>
--
Pavan Balaji
http://www.mcs.anl.gov/~balaji
More information about the mpich-discuss
mailing list