[torquedev] [torqueusers] Change in interactive job behavior from previous torque versions.
dbeer at adaptivecomputing.com
Thu Apr 15 10:13:50 MDT 2010
Just to clarify, I didn't check in the changes to make the new behavior parameterizable, since they don't restore the old exploit.
----- Original Message -----
> Hi all,
> When I talked to the developer who made this change, he told me that
> the old functionality likely only worked due to a bug. A few months
> back we fixed a bug related to input parsing - TORQUE was parsing qsub
> input twice. This was causing problems on submit filter scripts,
> because they were being run twice. This morning I made the new
> behavior parameterizable and found out that he was right: even if the
> new behavior is removed, the old behavior of reading the script for
> directives doesn't occur.
> In other words, the old behavior was an exploit of a bug in TORQUE.
> This is part of why we didn't know people were doing it. Now we have
> to look at where to go from here. How many people were using this
> ----- Original Message -----
> > Re: [torquedev] [torqueusers] Change in interactive job behavior
> > from previous torque versions.
> > On 15/04/10 04:56, Joshua Bernstein wrote:
> > > I had three people last week asked why this was changed.
> > It has caught people out here too, I didn't even realise
> > it was possible!
> > cheers,
> > Chris
> > -- Christopher Samuel - Senior Systems Administrator
> > VLSCI - Victorian Life Sciences Computational Initiative
> > Email: samuel at unimelb.edu.au Phone: +61 (0)3 903 55545
> > http://www.vlsci.unimelb.edu.au/
> > _______________________________________________ torquedev mailing
> > list torquedev at supercluster.org
> > http://www.supercluster.org/mailman/listinfo/torquedev
> -- David Beer | Senior Software Engineer
> Adaptive Computing
> _______________________________________________ torquedev mailing list
> torquedev at supercluster.org
David Beer | Senior Software Engineer
More information about the torquedev