[torqueusers] Problems with output on very short jobs

Ronny T. Lampert telecaadmin at uni.de
Fri Nov 25 11:57:12 MST 2005

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
>>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.

>>I'm somewhat suspecting a race condition as the used.mem attributes are also
> You won't see any usage until the job has run at least $check_poll_time
> seconds.

Can't be! Both jobs have 5 seconds walltime (way below job_stat_rate = 180),
one has resources used, one hasn't - both are idential jobs.

11/25/2005 16:32:28;0010;PBS_Server;Job;207535.rk001tsd.tsd.de;Exit_status=0
resources_used.cput=00:00:00 resources_used.mem=2748kb
resources_used.vmem=12464kb resources_used.walltime=00:00:05

11/25/2005 16:35:57;0010;PBS_Server;Job;207536.rk001tsd.tsd.de;Exit_status=0
resources_used.cput=00:00:00 resources_used.mem=0kb resources_used.vmem=0kb

So I'll give 2.0 a try and report back.


More information about the torqueusers mailing list