On Thu, 17 Jul 2014 15:14:19 +0200
Paolo Di Tommaso wrote:

Hi Paolo,

> Since I'm submitting many jobs, programmatically, by using an external
> tool, I would need a mechanism to get notified when jobs terminate and
> above all when some of them are killed. For this reason I would need a
> strategy other than a email message, that is not useful in this
> scenario.
> 
> Since the SGE kill jobs by sending a SIGTERM signal, there's no way to
> intercept it in the job script. So I can't invoke the mailer from it
> or implement any other strategy there.

We can configure "soft" resources limits and send a different signal.
You app picks it and does whatever you want.  (or you can send your jobs
with notify).

 
> Alternatives could be to use a epilog script or the "qacct" command,
> but unfortunately both of them are not available in SGE cluster of my
> institute.

We can also configure an epilog script (if it does not affect other
people's job), and qacct is now available for you.
(Other batch systems have epilogues based on users, let me check if ogs
also supports that).

> Thus, a custom mailer script is the only available option, I could
> use it to write the job notification to a file or even better to a
> socket. But I would need to do that at user level, I mean only for
> jobs submitted from my environment, without changing the default
> mailer for the other cluster users.
> 
> For this reason I'm wondering if the mailer SGE configuration can be
> defined in the user environment. I'm not sure but I seem to remember
> that it is possibile to define the sge_conf file somewhere in the
> user $HOME directory. Any clue about that?

AFAIK you cannot modify the mailer option (but maybe someone knows how
to do it).

> Thanks,
> Paolo
Cheers,
Arnau
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to