[torqueusers] The strange issue when submit job with pbs: libibverbs: Warning: RLIMIT_MEMLOCK is 32768 bytes. and so on.
Stijn De Weirdt
stijn.deweirdt at ugent.be
Mon Nov 14 08:07:36 MST 2011
we have the -n limit set like this as well, but if an application
doesn't use torque to start the mpi processes on the other nodes (eg
some mpi build without torque support and relying on eg ssh), how is
this limit then set?
> I'm not sure I'd go so far as to say it's definitely unrelated to
> Torque. We ran into a similar problem, and in the end it was a
> limitation imposed by the shell/environment when the pbs_mom started.
> Since jobs were child processes of the pbs_mom, they inherited the
> memory limits.
> Since we're using the RPM packages, and the contrib'd init script, the
> best solution was to put the following lines in /etc/sysconfig/pbs_mom;
> if you're using a different environment, etc., you may have to adjust
> the method you use to do something similar:
>> #installation-specific limits for pbs_mom
>> ulimit -l unlimited
>> ulimit -n 32768
> There are a lot of opinions about what the right limits to put here are,
> as well.
> Lloyd Brown
> On 11/13/11 2:25 AM, Stijn De Weirdt wrote:
>> this is unrelated to torque, but here's the relevant faq entry for openmpi
More information about the torqueusers