From owner-freebsd-doc Thu Jan 17 12:40: 9 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 46C0D37B41A for ; Thu, 17 Jan 2002 12:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0HKe2w75170; Thu, 17 Jan 2002 12:40:02 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8AD2937B417 for ; Thu, 17 Jan 2002 12:36:47 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0HKalX74823; Thu, 17 Jan 2002 12:36:47 -0800 (PST) (envelope-from nobody) Message-Id: <200201172036.g0HKalX74823@freefall.freebsd.org> Date: Thu, 17 Jan 2002 12:36:47 -0800 (PST) From: Steven Grady To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/34005: mmap man page description of ENOMEM is ambiguous Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34005 >Category: docs >Synopsis: mmap man page description of ENOMEM is ambiguous >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 17 12:40:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Steven Grady >Release: 4.3 >Organization: DigitalDeck, Inc. >Environment: FreeBSD inigo.digitaldeck.com 4.3-RELEASE-p20 FreeBSD 4.3-RELEASE-p20 #0: Wed Nov 7 21:15:47 PST 2001 mudie@inigo.digitaldeck.com:/usr/src/sys/compile/INIGO i386 >Description: The man page says under ENOMEM: MAP_FIXED was specified and the addr parameter wasn't available, or the system has reached the per-process mmap limit specified in the vm.max_proc_mmap sysctl. MAP_ANON was specified and insufficient memory was available. This _could_ be taken to mean that the max_proc_mmap limit is only applicable when MAP_FIXED is specified. It took me a while to track down an ElectricFence failure because I misinterpreted this line. >How-To-Repeat: >Fix: Change to something like the following. MAP_FIXED was specified and the addr parameter wasn't available. The system has reached the per-process mmap limit specified in the vm.max_proc_mmap sysctl. MAP_ANON was specified and insufficient memory was available. (I.e. separate the max_proc_mmap line from the MAX_FIXED line, to make it clear that they are independent.) >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message