[mvapich-discuss] mvapich locked memory limit and queuing system

[Noam Bernstein]

Has anyone noticed a conflict between OFED/mvapich's desire for a  
large locked memory
limit and the queuing system?   I've upped the memlock  limit in /etc/ 
security/limits.conf
(and rebooted, so the queuing system daemons should be seeing the  
larger limit).
This allows me to run interactively.  However, jobs submitted through  
our queuing system
(SGE 6.0) still see the low memlock limit (32 kB), and can't increase  
the limit.  I found a brief
discussion of a similar problem in torque (this thread:
http://www.beowulf.org/archive/2006-May/015559.html
), but no apparent solution.

Has anyone seen this problem, and preferably discovered a solution?

											thanks,
											Noam