[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Condor-users] Notification of Cluster Complete - not processcomplete

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Zachary Miller
> Sent: 29 July 2004 19:09
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Notification of Cluster Complete - not
> processcomplete
> > 
> > Disable all email notification (apart from maybe errors)
> > After submitting the jobs run condor_wait pointing at the resulting clusterid
> > and have that launch some simple mail script to send the mail.
> i think it would be slightly better to submit condor_wait as 
> a condor job
> itself, and then have that job email you when it's finished.  
> no scripts
> necessary, and if the machine goes down for some reason, your 
> condor_wait
> process will come back up when condor does.

Though this would have the side effect of tacking up a slot either on your pool or on your local machine which may be problematic if you run more concurrent clusters
that you have free slots to run your wait jobs. A nicer though more complex solution is to create some service (or *nix equiv) which is informed of clusters it is meant to watch (simple web service may well be ideal) and this fires off a condor wait process. Then you just need to deal with persisting state. 

Alternate is to setup a new pool just for this but that seems somewhat excessive...


Gloucester Research Limited believes the information 
provided herein is reliable. While every care has been 
taken to ensure accuracy, the information is furnished 
to the recipients with no warranty as to the completeness 
and accuracy of its contents and on condition that any 
errors or omissions shall not be made the basis for any 
claim, demand or cause for action.