Re: [Condor-users] Wildcard in transfer_input_files?

[Matthew Farrellee <matt@xxxxxxxxxx>]

On 09/26/2012 04:51 AM, Ian Cottam wrote:
> On 25/09/2012 21:08, "Matthew Farrellee" <matt@xxxxxxxxxx> wrote:
>
> > On 09/25/2012 01:55 PM, Ian Cottam wrote:
> > > On 22/09/2012 15:17, "Matthew Farrellee" <matt@xxxxxxxxxx> wrote:
> > >
> > >
> > > > Or use -append, condor_submit -append "transfer_input_files = $(echo
> > > > *.data)" my.job
> > > >
> > > > Best,
> > > >
> > > >
> > > > matt
> > >
> > > I'm interested in other examples of -append that people use.
> > > For example, I imagine  -append "initialdir = test"  could be useful for
> > > switching between test and live data.
> > > -Ian
> >
> > Pure CLI submission: echo queue 3 | condor_submit -a cmd=/bin/cat -a
> > args=/proc/self/status -a 'output=status.$(process).out'
> >
> > I do this a lot to skip writing submit files.
> >
> > Best,
> >
> >
> > matt
>
> A variation that would be nice is to have a submit file with no Queue
> line, and then add it with
>
> -append "queue 5000" or -append "queue 1". The latter being useful for
> testing.
>
> The Condor rule that says a submit file must have a queue line prevents
> this scenario.
> -Ian

You can do it indirectly,

$ cat append.job
cmd = /bin/hostname
output = hostname.$(process).out
queue $(count)

$ condor_submit -a count=3 append.job
Submitting job(s)...
3 job(s) submitted to cluster 124.

$ condor_submit append.job
Submitting job(s).
1 job(s) submitted to cluster 125.

Best,


matt