On 03/06/16 16:24, Riccardo Murri wrote:
Hi Kenneth, all,
So, although 'qstat -f' is an alternative you can certainly support, it's
not general enough to work with a 'standard' Torque setup.
A possible alternative is that GC3Pie submits an epilogue script for each
job it submits, to capture the exit code (& more) of the job...
See
http://docs.adaptivecomputing.com/torque/4-1-4/Content/topics/12-appendices/perJobPrologueAndEpliogueScripts.htm
Thanks, this looks like a good idea. But it's quite different from what
the other batch systems do/provide, so shorter-term parsing `qstat -f`
looks more viable.
Two more questions:
1- Can the user-provided epilogue scripts be turned off server-side? In
other words, would this epilogue.user thing work on *every* site
running TORQUE?
Well, I'd like to say it'll likely work everywhere, but it doesn't seem
to work even for us...
The alternative via "qsub -T" doesn't seem to work either...
So, I guess your best option is to add extra stuff to the end of the job
script?
Not sure how reliable that is though...
2- The docs are somewhat terse as to the actual format of the info
passed to the epilogue.user script. Can you please run an
epilogue.user script that prints $argv[1] up to $argv[10] and send me
the output? E.g.
I'd love to provide it, but... ^^^ ;-)
K.
#! /bin/bash
echo Sample epilogue.user
echo ========
echo argv1=$1
echo argv2=$2
echo argv3=$3
echo argv4=$4
echo argv5=$5
echo argv6=$6
echo argv7=$7
echo argv8=$8
echo argv9=$9
echo argv10=${10}
Thanks,
R
--
Riccardo Murri
http://www.s3it.uzh.ch/about/team/#Riccardo.Murri
S3IT: Services and Support for Science IT
University of Zurich
Winterthurerstrasse 190, CH-8057 Zürich (Switzerland)
Tel: +41 44 635 4208
Fax: +41 44 635 6888
