[torqueusers] qpeek in contrib

Gareth.Williams at csiro.au Gareth.Williams at csiro.au
Tue Jul 31 15:13:38 MDT 2012

> -----Original Message-----
> From: Craig Tierney [mailto:craig.tierney at noaa.gov]
> Sent: Wednesday, 1 August 2012 4:39 AM
> To: torqueusers at supercluster.org
> Subject: Re: [torqueusers] qpeek in contrib
> On 7/31/12 4:35 AM, Gareth.Williams at csiro.au wrote:
> > Hi,
> >
> > We've found a need for a command to look at jobs output before it is
> > finished so tried the qpeek script from OSC in the torque contrib
> directory.  With a few minor mods it works fine but I want to check a
> few things (different people may be needed to answer each question):
> >
> > 1) That qpeek is marked: Copyright 2001, Ohio Supercomputer Center
> but
> > with no author or licensing info. Since it is clearly in a
> > contrib(uted) section of an open source project I'm assuming that
> modifying it for local use is fair game - though I'd be cautious about
> redistributing changes.  Does anyone know better?
> >
> > 2) If I improve that qpeek, who might I contribute the changes back
> to?
> >
> > 3) Does anyone have an alternative to share?  I see nf.nci.org.au has
> > a qcat which serves a similar purpose with a mixture of more and less
> functionality (it will also show the script but does not head, tail or
> follow).
> >
> > Frankly I'd prefer not to write my own!
> >
> Gareth,
> Do you have a shared filesystem between your systems?
> If so, why not enable "$spool_as_final_name true" in mom_priv/config.
> http://www.adaptivecomputing.com/resources/docs/torque/2-5-
> 9/a.cmomconfig.php
> Craig

Hi Craig,

Thanks but that is pretty much the situation we are trying to avoid!  We are finding that many small writes to a shared filesystem cause a performance impact. We figure users are writing to a shared filesystem because they want feedback so if we can give them a qpeek, they can be happy to spool the small writes to a local filesystem instead.


More information about the torqueusers mailing list