[torqueusers] Problems with output on very short jobs
garrick at usc.edu
Fri Nov 25 12:24:47 MST 2005
On Fri, Nov 25, 2005 at 07:57:12PM +0100, Ronny T. Lampert alleged:
> OOPS, wrong sender.
> -------- Original Message --------
> > Lots and lots of bugfixes since then.
> I know, I am not that unactive here ;)
> >>Job script looks like:
> >>eval "HResults -PARAMS > output.eval && hresults2pvset.pl output.eval
> >>-PARAMS 1> OUTPUT 2> OUTPUT2"
> >>sleep 5
> > The job doesn't print anything to stdout or stderr so I would expect
> > empty output files.
> The jobs does only look like this above; there are a couple of echo "stuff"
> in there, so there MUST be output.
> As I said: sometimes there IS output, sometimes there ISNT.
Try the 2.0.0p3 snapshot from yesterday. On Wednesday I did some code
clean-up in the file copy functions and fixed up some error reporting.
In short, configure with --enable-syslog, turn MOM's loglevel to 6, and
watch your syslog output.
Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20051125/5720c58d/attachment.bin
More information about the torqueusers