[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor Call back mechanism
- Date: Thu, 31 May 2007 07:20:57 -0500
- From: "Erik Paulson" <epaulson@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] Condor Call back mechanism
On 5/31/07, Kewley, J (John) <j.kewley@xxxxxxxx> wrote:
One of the config values is the location of the mail program. I have
considered using my
own program there instead and parsing the "mail message" sent to it, but
have never tried it.
I'd be interested in finding out if that was possible.
I don't see why it wouldn't work, though obviously the mail messages
aren't the most parse-friendly pieces of data.
Another option is to use DAGMan with a POST script for each job to
submit your jobs. You can have a very wide DAG with no parent-child
relationships, and your jobs basically run just as before.
Another option is to tail the job logfile yourself, and when you see a
terminate event you can do whatever you want. (Tailing the logfile is
how DAGMan works) If you use the Condor Perl module, you can register
a perl subroutine as a callback and it will take care of the tailing
for you, and you can register different callbacks on different sorts
of exits (one callback for exit with success, a callback for exit with
failure, a callback for evicted, etc). The only bummer about the perl
module is you have to let the perl module do the submitting (again,
[mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of
Sent: Thursday, May 31, 2007 6:10 AM
Subject: [Condor-users] Condor Call back mechanism
I have a question on Condor Call back mechanism.
When it finishes a job, it can send email that the job is done. But is it
possible to take some other action like "executing a shell script" or
putting a message in MQ.
Basically we like to do some thing other than just getting email when the
job is complete by Condor.
Is there any way to achieve this ?
Palate Teasers: Straight from Master Chef! Sanjeev Kapoor
Condor-users mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: