Thanks Daniel, I now have the C program being run when I run qsub w/the -m aebs 
-M william.l...@cshs.org
command line options.

However, when I look at the parameters being passed to the C program via 
main(int argc, char** argv)

    FILE *outfile;            /*output file outfile for debugging*/

    outfile = fopen("out.txt","wt");
    if (outfile == NULL){
       fprintf(stderr, "\nCouldn't open file out.txt\n");
    }

    fprintf(outfile,"argc = %d\n", argc);

    for (i = 0; i < argc; i++)
        fprintf(outfile,"argv[%d] = \"%s\"\n", i, argv[i]);

    fclose(outfile);

I'm getting:

     argc = 4
     argv[0] = "mail"
     argv[1] = "-s"
     argv[2] = "Job 203 (mpirun) Aborted"
     argv[3] = "william.l...@cshs.org"

Why isn't the body of the message being passed as an argument? I'm not seeing a 
message body
that has the statistics of the job (i.e. start time, end time, exit code etc.).

Is there a C SGE API where I could directly query the SGE mySQL DB and get the 
start time and
end time of a job based on the job number parsed from the subject?

-Bill L.


________________________________
From: users-boun...@gridengine.org [users-boun...@gridengine.org] on behalf of 
Daniel Gruber [dgru...@univa.com]
Sent: Tuesday, October 20, 2015 12:37 AM
To: Lane, William
Cc: users@gridengine.org
Subject: Re: [gridengine users] Trying to code C program to process SGE 
job-status email

Hi Bill,

You changed the global configuration (qconf -mconf or qconf -mconf global).
This is most likely overridden by the host local configuration.
Try with changing it in the host local configuration (qconf -mconf <hostname>).
You are right it takes a few seconds that the changes are propagated but
it is done automatically.

Daniel


Am 20.10.2015 um 09:24 schrieb Lane, William 
<william.l...@cshs.org<mailto:william.l...@cshs.org>>:

I've been trying to code a C program to process the SGE job-status email to
determine if a job failed due to exceeding the h_rt limitation of a defined 
queue.

I have a defined queue short.q w/a h_rt runtime limit of 9 secs.

I modified, via qconf -mconf the mailer line as follows:

     execd_spool_dir                 /opt/sge/default/spool
     mailer                       /usr/sbin/SGEProcessEmail.out
     xterm                       /usr/bin/xterm

However when I run my linpack test benchmark (the runtime of which
exceeds a minute), I'm still getting email as if the mailer line was reading
/usr/sbin/sendmail. My binary /usr/sbin/SGEProcessEmail.out isn't getting 
executed
at all, even though it has world rwx privileges set.

When I test the code from a command-line it works as expected.

Do I have to somehow propagate these changes to the exechost/compute nodes?

Thank you in advance.

-Bill L.


IMPORTANT WARNING: This message is intended for the use of the person or entity 
to which it is addressed and may contain information that is privileged and 
confidential, the disclosure of which is governed by applicable law. If the 
reader of this message is not the intended recipient, or the employee or agent 
responsible for delivering it to the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this information is 
strictly prohibited. Thank you for your cooperation.
_______________________________________________
users mailing list
users@gridengine.org<mailto:users@gridengine.org>
https://gridengine.org/mailman/listinfo/users

IMPORTANT WARNING: This message is intended for the use of the person or entity 
to which it is addressed and may contain information that is privileged and 
confidential, the disclosure of which is governed by applicable law. If the 
reader of this message is not the intended recipient, or the employee or agent 
responsible for delivering it to the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this information is 
strictly prohibited. Thank you for your cooperation.
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to