[GE users] Jobs leave orphaned processes behind

reuti reuti at staff.uni-marburg.de
Mon Aug 30 17:38:05 BST 2010


Hi,

Am 30.08.2010 um 18:24 schrieb isakrejda:

> I am trying to understand without diving into user's rather complex workflow
> what might be causing  orphaned processes to be left behind when user's
> job is killed by a time limit.
> 
> Usually SGE kills all the child processes cleanly, but with this one case we
> are having problems. Are there any well known loopholes that I am not aware of?

for some applications they start a new process group and can't be caught by the usual kill of the process group. Setting:

execd_params                 ENABLE_ADDGRP_KILL=TRUE

in SGE's configuration should help. If not, it must be investigated why the job isn't tightly integrated into SGE.

-- Reuti


> Grateful for hints,
> 
> Iwona
> 
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=278262
> 
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=278268

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list