Hi,
Experiencing an odd issue that I can seemingly only blame on torque.
Would love some assistance.
[brett@tango ping]$ ssh tango010 ulimit -l
unlimited
[brett@tango ping]$ qsub -l nodes=tango010:ppn=2 -l walltime=0:5:0 -I
qsub: waiting for job 22605.tango-m.vpac.org to start
qsub: job 22605.tango-m.vpac.org ready
[brett@tango010 ~]$ ulimit -l
32
[brett@tango010 ~]$ grep -i unlimited /etc/security/limits.conf
* soft memlock unlimited
* hard memlock unlimited
Why is torque limiting the memlock so low, and how can I stop it from
doing this?
what is even stranger:
[brett@tango ping]$ qsub -l nodes=tango001:ppn=2 -l walltime=0:5:0 -I
qsub: waiting for job 22606.tango-m.vpac.org to start
uqsub: job 22606.tango-m.vpac.org ready
[brett@tango001 ~]$ ulimit -l
unlimited
why is it only doing it on SOME nodes ?
I'm quite baffled by this.
thanks,
/ Brett
--
Brett Pemberton - VPAC Systems Programmer
http://www.vpac.org/ - (03) 9925 4899
signature.asc
Description: This is a digitally signed message part
_______________________________________________
torqueusers mailing list
torqueusers@xxxxxxxxxxxxxxxx
http://www.supercluster.org/mailman/listinfo/torqueusers
| 
