Re: [Condor-users] Notification of Cluster Complete - notprocesscomplete

[Erik Paulson <epaulson@xxxxxxxxxxx>]

On Thu, Jul 29, 2004 at 07:47:04PM +0100, Matt Hope wrote:
> > -----Original Message-----
> > From: condor-users-bounces@xxxxxxxxxxx
> > [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Erik Paulson
> > Sent: 29 July 2004 19:35
> > To: Condor-Users Mail List
> > Subject: Re: [Condor-users] Notification of Cluster Complete - not
> > processcomplete
> 
> > > 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
> > 
> > No, you would submit the job as a "scheduler universe" job. Scheduler universe
> > jobs run on the submit machine - they're not matched, so you can run as many of 
> > them as you want. DAGMan is the prime example of a scheduler universe job - 
> > run 'condor_submit_dag -nosubmit' to see what it would tell the schedd to
> > do.
> 
> Ah.. I see what Zach meant now - can you submit any executable into the scheduler universe or does it have to be wrapped in a dag?
> 

Anything you want. We use this one all the time:

executable = /bin/hostname
output = hostname.output
log  = hostname.log
queue

And Condor will run /bin/hostname for you. 

-Erik