mlock(2), unprivileged users, and RLIMIT_MEMLOCK

[Joe Marcus Clarke]

On Sat, 2008-04-12 at 22:16 -0400, Coleman Kane wrote:

> It turns out that in order to use some commands (such as ps, w, top, and
> others), you'll need a memorylocked limit even higher. I have mine at
> around 250 right now and so far it seems to be fine. If you don't do
> this, then these programs will spin in an infinite loop attempting to
> allocate some memory (which the system refuses).

Yeah, as I said, quite a few sysctl handlers user vslock() which wires
memory. Some of the bigger ones are the new procstat sysctls.  I wonder
how gnome-system-monitor and procstat work with a limited
RLIMIT_MEMLOCK.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team      ::      gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20080413/6f828ddc/attachment.pgp