[gridengine users] emails when -M not in script?

Reuti reuti at staff.uni-marburg.de
Mon Jul 25 22:41:39 UTC 2011


Am 25.07.2011 um 23:17 schrieb Mike Hanby:

> This may be a bug, but testing the ~/.sge_request approach produced the following results:
> 
> * qsub job without the -M arg, email was delivered to the address specified in ~/.sge_request
> * qsub job with -M and two emails are sent, one to the qsub -M email, the other to the one in ~/.sge_request
> 
> Instead of overwriting the maillist, multiple -M's apparently append to the current maillist. Bummer.

A list of addresses is valid in principle.

The man page of `qsub` states the same beginning "Defines or redefines" for -M as for -q, and for -q it was an issue of some time until it got fixed and replaced the given wc_queue_list.

I would suggest to file an issue.

-- Reuti


>> -----Original Message-----
>> From: users-bounces at gridengine.org [mailto:users-
>> bounces at gridengine.org] On Behalf Of Mike Hanby
>> Sent: Monday, July 25, 2011 4:11 PM
>> To: 'Reuti'; Mark Suhovecky
>> Cc: users at gridengine.org
>> Subject: Re: [gridengine users] emails when -M not in script?
>> 
>> What about adding
>> 
>> -M default_admin at mydom.com
>> 
>> or whatever to /opt/gridengine/default/common/sge_request (adjust path
>> to suit your env)
>> 
>> Alternatively, create a ~/.sge_request file for each user (add this to
>> your user account creation script) and assign their default email addy
>> there:
>> 
>> cat ~jondoe/.sge_request
>> 
>> -M jondoe at example.com
>> 
>> Mike
>> 
>>> -----Original Message-----
>>> From: users-bounces at gridengine.org [mailto:users-
>>> bounces at gridengine.org] On Behalf Of Reuti
>>> Sent: Friday, July 22, 2011 2:24 PM
>>> To: Mark Suhovecky
>>> Cc: users at gridengine.org
>>> Subject: Re: [gridengine users] emails when -M not in script?
>>> 
>>> Am 22.07.2011 um 21:11 schrieb Mark Suhovecky:
>>> 
>>>> Occasionally users submit SGE scripts on our system without the -M
>>> option set.
>>>> I would expect these to go to admin_mail address defined under the
>>> general cluster settings;
>>>> instead, they're going to root on the local compute node. Is there
>>> something missing in my settings?
>>>> Can I configure this behavior?
>>> 
>>> But the nodes can send to the outside world?
>>> 
>>> Usually postfix needs to be set up on the nodes to use the headnode
>> as
>>> a relay. Then the users can just define their real email address in
>>> ~/.forward and it will reach them all the time. It might also be
>>> necessary to change the sender, as root at node01 might be rejected by
>>> some MTAs.
>>> 
>>> Or you set it up for all in /etc/aliases
>>> 
>>> (Second way: Using a JSV to attach an email address to the jobs would
>>> need to look up in a database or the above file, whereto to send the
>>> emails. The forwarding must be set up anyway.)
>>> 
>>> -- Reuti
>>> 
>>> 
>>>> I took a quick stab at finding threads on this in the old
>>> mailmark.org archives, but came up empty.
>>>> 
>>>> Thanks for any input,
>>>> 
>>>> Mark
>>>> 
>>>> Mark Suhovecky
>>>> HPC System Administrator
>>>> Center for Research Computing
>>>> University of Notre Dame
>>>> suhovecky at nd.edu
>>>> _______________________________________________
>>>> users mailing list
>>>> users at gridengine.org
>>>> https://gridengine.org/mailman/listinfo/users
>>> 
>>> 
>>> _______________________________________________
>>> users mailing list
>>> users at gridengine.org
>>> https://gridengine.org/mailman/listinfo/users
>> 
>> _______________________________________________
>> users mailing list
>> users at gridengine.org
>> https://gridengine.org/mailman/listinfo/users
> 
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users





More information about the users mailing list