From owner-freebsd-security  Fri Dec 24 10:52:56 1999
Delivered-To: freebsd-security@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6652415250; Fri, 24 Dec 1999 10:52:50 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA03403;
	Fri, 24 Dec 1999 10:52:49 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id KAA71968;
	Fri, 24 Dec 1999 10:52:48 -0800 (PST)
	(envelope-from jdp@polstra.com)
Message-ID: <XFMail.991224105248.jdp@polstra.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3863B98A.A3888539@dnai.com>
Date: Fri, 24 Dec 1999 10:52:48 -0800 (PST)
Organization: Polstra & Co., Inc.
From: John Polstra <jdp@polstra.com>
To: Michael Sierchio <kudzu@dnai.com>
Subject: RE: mlockall() not supported (2nd query)
Cc: freebsd-core@freebsd.org, freebsd-security@freebsd.org
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Michael Sierchio wrote:
> mlockall() and munlockall() don't appear to be supported on FreeBSD.

The most effective way to get them supported is to submit patches.
From a quick look at mlock() in "src/sys/vm/vm_mmap.c", it doesn't
look all that difficult.

John



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message