Apologies if this has already been discussed, but is it the case that some
SAME tests now get run within the job wrapper? I remember seeing something
about this at some stage and looking on a node where I'm running a simple
/bin/hostname using globus-job-run I see this kind of stuff:
6142 7118 0.3 2.6 9372 6848 ? S 09:19 0:01 python
/opt/lcg/same//client/bin/same-exec --nodetest WN gridmon.cs.tcd.ie --
stage=start.stage1
sh_results=/home/gitest042/globus-tmp.gridmon.6767.0/.same_result.xq7111
sh_results_all=/home/gitest042/globus-tmp.gridmon.6767.0/.same_details.Fv7113
starttime=1174468780
stage2_dir=/home/gitest042/globus-tmp.gridmon.6767.0/.same_stage2.oF7109
Of course the problem is that the SAME stuff is getting stuck at the
moment. Is there any way to disable it?
Stephen
--
Dr. Stephen Childs,
Research Fellow, EGEE Project, phone: +353-1-8961797
Computer Architecture Group, email: Stephen.Childs @ cs.tcd.ie
Trinity College Dublin, Ireland web: http://www.cs.tcd.ie/Stephen.Childs
|