[torqueusers] qsub patch for job script arguments.

Roy Dragseth roy.dragseth at cc.uit.no
Fri Sep 2 01:05:04 MDT 2011


On Tuesday, August 30, 2011 09:11:19 Bas van der Vlies wrote:
> On 30-08-11 00:46, Michael Jennings wrote:
> > On Tuesday, 30 August 2011, at 08:43:09 (+1000),
> > 
> > Gareth.Williams at csiro.au wrote:
> >> I like the -- idea, but I think it is more natural to have (or at least
> >> allow) -- before the job script: qsub -- run.sh arg1 arg2
> >> Before is better to signify that qsub options are complete and the rest
> >> of the line is the job script and its options.  After still signifies
> >> this but splits the job script and its options unnecessarily.
> > 
> > That doesn't work.  The job script is an argument to qsub.  The
> > convention is that -- halts option parsing; the command is supposed to
> > ignore anything that comes after --.  If qsub ignores the jobscript
> > name, not much will get done.  ;-)
> > 
> > Using -- is by far the simplest and most standard approach IMHO.
> > Either that, or just ignore everything after the jobscript name.
> 
> I am also for -- solution. As said it is a standard approach and seen a lot
> in other software.

I would strongly argue for the -- approach as an addition to the -F flag.  If 
there are any technical issues with the patch please let me know.

r.


More information about the torqueusers mailing list