Hi,

Am 22.03.2018 um 20:51 schrieb Mun Johl:

> Hi,
>  
> I’m using SGE v8.1.9 on RHEL6.8 .  In my script that I submit via qsub (let’s 
> call it scriptA), I have a gxmessage (gxmessage is similar to xmessage, 
> postnote, etc) statement which pops up a small status window notifying the 
> user of the results of the qsub job.

Is SGE and your job running local on your workstation only? I wonder how the 
gxmessage could display something on the terminal of the user when the job runs 
on an exechost in the cluster and was submitted at some time in the past.


>  However, I don’t want the gxmessage to exit when scriptA terminates.  So 
> far, I have not figured out a what to satisfy my wants.  That is, when 
> scriptA terminates, so does gxmessage.  nohup  does not help because 
> gxmessage gets a SIGKILL.

SGE kills the complete process group when the jobs ends (or is canceled), not 
just a single process. One might circumvent this with a `setsid foobar &` 
command. The `nohup` isn't necessary here.

As a second measure to kill orphaned processes one can use the additional group 
id, which is attached to all SGE processes. Although it would be 
counterproductive in your case as it would kill the leftover process despite 
the newly created process group. This would need to set:

$ qconf -sconf
#global:
...
execd_params                 ENABLE_ADDGRP_KILL=TRUE

You can use:

$ ps -e f -o pid,ppid,pgrp,session,command

on the exechost to investigate this (f w/o dash, it's not a typo)


> Is it a “feature” of SGE to ensure all child processes are dead when the qsub 
> job terminates?

Yes, this is a feature of SGE and usually highly welcome.

-- Reuti


>  Is there a way I can allow scriptA to terminate but leave behind a child 
> process on a qhost?
>  
> I have a workaround for this issue, but at this point I really want to 
> understand what SGE is doing and if there are better solutions than what I 
> have in mind for my workaround.
>  
> Thanks,
>  
> --
> Mun
> _______________________________________________
> users mailing list
> users@gridengine.org
> https://gridengine.org/mailman/listinfo/users


_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to