[mvapich-discuss] problem w/MVAPICH in the frames of Gen1

Jimmy Tang jtang at tchpc.tcd.ie
Thu Aug 10 14:25:19 EDT 2006


Hi Mikhail,

On Thu, Aug 10, 2006 at 10:02:27PM +0400, Mikhail Kuzminsky wrote:
> In message from Andrey Slepuhin <andrey.slepuhin at t-platforms.ru> (Thu, 
> 10 Aug 2006 21:17:37 +0400):
> >So, the problem is with memory locking - see the failed mlock() in the 
> >end of output. Regardless of rlimits you also may have memlock 
> >capability enabled only for root - I don't remember exact /proc entry, 
> >where you can disable it, but you can try to search it.
> 
> Yes, may be sysctl -w vm.disable_cap_mlock=1
> (proposed here sometime ago) performs this job (I don't know exactly
> the sense of this key), but my /proc don't have this file. I also 
> didn't find any file (in /proc) having "mlock" context.
> 
---end quoted text---

perhaps doing a "sysctl -a | less" and see what resembles
vm.disable_cap_mlock (which is sles9 2.6 kernel) on the system you are
on?

or if you are really daring and really trust your users (and the software
you are running in terms of security) perhaps you can try setting the
suid bit on various pieces of software you are using. though its
probably a bad idea :)

Jimmy.

-- 
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/


More information about the mvapich-discuss mailing list