[torquedev] Re: [torqueusers] Rerunnable Flag

Garrick Staples garrick at usc.edu
Thu Aug 21 11:51:08 MDT 2008

On Thu, Aug 21, 2008 at 10:50:42AM -0400, Glen Beane alleged:
> On Wed, Aug 20, 2008 at 6:51 AM, Chad Vizino <vizino at psc.edu> wrote:
> > We have changed the default at our site to *not* rerunnable.  Check out
> > src/server/req_quejob.c to change the default at the server.  Look for the
> > comment:
> >
> >      /* Interactive jobs are necessarily not rerunable */
> >
> > And get rid of the "if" condition around these lines just after that:
> >
> >      pj->ji_wattr[(int)JOB_ATR_rerunable].at_val.at_long = 0;
> >      pj->ji_wattr[(int)JOB_ATR_rerunable].at_flags |= ATR_VFLAG_SET;
> wouldn't this make every job non rerunnable?  I think Chris had the right
> idea, patch qsub so by default if the user does not specify the rerunable
> flag it does not default to true.
> We could easily make the default FALSE in qsub if no one has any reason to
> object (or make it a ./configure option)

Build-time flags are bad.  Makes it hard to distribute binaries.

Just add a another parameter to torque.cfg.  That's where qsub's other run-time
defaults go.

Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20080821/700baa5c/attachment-0001.bin

More information about the torquedev mailing list