also, limits.conf is set when starting a ssh session. it is not useful for services started at boot time, and ulimit -l unlimited should be added in the startup script /etc/init.d/xxx or /etc/sysconfig/xxx
Cheers, Gilles On Thursday, March 17, 2016, Dave Love <d.l...@liverpool.ac.uk> wrote: > Michael Di Domenico <mdidomeni...@gmail.com <javascript:;>> writes: > > > On Wed, Mar 16, 2016 at 12:12 PM, Elken, Tom <tom.el...@intel.com > <javascript:;>> wrote: > >> Hi Mike, > >> > >> In this file, > >> $ cat /etc/security/limits.conf > >> ... > >> < do you see at the end ... > > >> > >> * hard memlock unlimited > >> * soft memlock unlimited > >> # -- All InfiniBand Settings End here -- > >> ? > > > > Yes. I double checked that it's set on all compute nodes in the > > actual file and through the ulimit command > > Is limits.conf actualy relevant to your job launch? It's normally used > by pam_limits (on GNU/Linux) which won't necessarily be run. [In the > case of SGE, you specify the resource limit as a parameter of the > execution daemon (execd), at least with "builtin" remote startup.] > > I'd verify it by executing something like "procenv -l" under mpirun. > (procenv is packaged for the major GNU/Linux distributions.) > _______________________________________________ > users mailing list > us...@open-mpi.org <javascript:;> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/03/28728.php >
