From dada@balu.kfunigraz.ac.at Sun May  9 06:44:14 1999
Return-Path: <dada@balu.kfunigraz.ac.at>
Received: from kaa.kfunigraz.ac.at (KAA16.kfunigraz.ac.at [143.50.16.17])
	by hub.freebsd.org (Postfix) with ESMTP id 1715B14F5C
	for <FreeBSD-gnats-submit@freebsd.org>; Sun,  9 May 1999 06:43:48 -0700 (PDT)
	(envelope-from dada@balu.kfunigraz.ac.at)
Received: from balu.kfunigraz.ac.at (balu [143.50.16.16])
	by kaa.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id PAA05985
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 May 1999 15:43:04 +0200 (MDT)
Received: from localhost.kfunigraz.ac.at (IDENT:NaWYpFR1amE8i3WUHEvNX180LDX9tWYL@BONLINEA11.kfunigraz.ac.at [143.50.36.11])
	by balu.kfunigraz.ac.at (8.9.2/8.9.2) with ESMTP id PAA23937
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 May 1999 15:43:41 +0200 (MDT)
Received: (from dada@localhost)
	by localhost.kfunigraz.ac.at (8.8.8/8.8.8) id PAA01254;
	Sun, 9 May 1999 15:42:03 +0200 (CEST)
	(envelope-from dada)
Message-Id: <199905091342.PAA01254@localhost.kfunigraz.ac.at>
Date: Sun, 9 May 1999 15:42:03 +0200 (CEST)
From: dada@sbox.tu-graz.ac.at
Sender: dada@balu.kfunigraz.ac.at
Reply-To: dada@sbox.tu-graz.ac.at
To: FreeBSD-gnats-submit@freebsd.org
Subject: RLIMIT_MEMLOCK not implemented
X-Send-Pr-Version: 3.2

>Number:         11607
>Category:       docs
>Synopsis:       RLIMIT_MEMLOCK not implemented
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May  9 06:50:01 PDT 1999
>Closed-Date:    Sat Jun 26 17:29:17 PDT 1999
>Last-Modified:  Sat Jun 26 17:30:34 PDT 1999
>Originator:     Martin Kammerhofer
>Release:        FreeBSD 2.2.8-STABLE i386
>Organization:
Graz University of Technology
>Environment:
>Description:

The per process limit on locked memory is not implemented.
(The shared system wide limit works though).
Until this will be eventually fixed manpages
getrlimit(2) and mlock(2) should note this in their BUGS section!

Also mlock/munlock are (currently) only available to the superuser
and return EPERM if called by a mere mortal. This behaviour should
be _documented_ in mlock(2).

>How-To-Repeat:

1. Call mlock() from non-root process => fails with EPERM.
2. Set RLIMIT_MEMLOCK to a small value. Mlock much more => works.

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Sat Jun 26 17:29:17 PDT 1999 
State-Changed-Why:  
The man page was updated to reflect that mlock/munlock can only 
be called by the super-user and the we do not currently support 
per-process limits via the RLIMIT_MEMLOCK mechanism. 
>Unformatted:
