From bmah@eisenhower.ca.sandia.gov Fri Mar 26 15:18:07 1999
Return-Path: <bmah@eisenhower.ca.sandia.gov>
Received: from eisenhower.ca.sandia.gov (eisenhower.ca.sandia.gov [146.246.243.57])
	by hub.freebsd.org (Postfix) with ESMTP id A0FBC15545
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 26 Mar 1999 15:00:19 -0800 (PST)
	(envelope-from bmah@eisenhower.ca.sandia.gov)
Received: (from bmah@localhost)
	by eisenhower.ca.sandia.gov (8.9.2/8.9.2) id OAA00562;
	Fri, 26 Mar 1999 14:59:59 -0800 (PST)
	(envelope-from bmah)
Message-Id: <199903262259.OAA00562@eisenhower.ca.sandia.gov>
Date: Fri, 26 Mar 1999 14:59:59 -0800 (PST)
From: bmah@ca.sandia.gov
Sender: bmah@eisenhower.ca.sandia.gov
Reply-To: bmah@ca.sandia.gov
To: FreeBSD-gnats-submit@freebsd.org
Subject: LINT configuration MAXDSIZ/DFLDSIZ misleading
X-Send-Pr-Version: 3.2

>Number:         10812
>Category:       kern
>Synopsis:       LINT configuration MAXDSIZ/DFLDSIZ misleading
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 26 15:20:01 PST 1999
>Closed-Date:    Sun Oct 22 15:04:49 PDT 2000
>Last-Modified:  Sun Oct 22 15:05:37 PDT 2000
>Originator:     Bruce A. Mah
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
Sandia National Laboratories
>Environment:

	

>Description:

The LINT configuration is a little misleading about settings for
MAXDSIZ and DFLDSIZ.  It looks like the comments didn't quite keep
up with rev 1.30 of src/sys/i386/include/vmparam.h.

>How-To-Repeat:

	

>Fix:

This patch makes the LINT file more consistent with 
src/sys/i386/include/vmparam.h.
	
--- LINT.old	Fri Mar 26 13:55:05 1999
+++ LINT	Fri Mar 26 14:14:23 1999
@@ -29,17 +29,18 @@
 maxusers	10
 
 #
-# Certain applications can grow to be larger than the 128M limit
+# Certain applications can grow to be larger than the 512M limit
 # that FreeBSD initially imposes.  Below are some options to
-# allow that limit to grow to 256MB, and can be increased further
+# allow that limit to grow to 1024M, and can be increased further
 # with changing the parameters.  MAXDSIZ is the maximum that the
 # limit can be set to, and the DFLDSIZ is the default value for
 # the limit.  You might want to set the default lower than the
 # max, and explicitly set the maximum with a shell command for processes
-# that regularly exceed the limit like INND.
+# that regularly exceed the limit like INND.  Without these options
+# specified, the normal value for MAXDSIZ is 128M and DFLDSIZ is 512M.
 #
-options		"MAXDSIZ=(256*1024*1024)"
-options		"DFLDSIZ=(256*1024*1024)"
+options		"MAXDSIZ=(256UL*1024*1024)"
+options		"DFLDSIZ=(1024UL*1024*1024)"
 
 # When this is set, be extra conservative in various parts of the kernel
 # and choose functionality over speed (on the widest variety of systems).

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: johan 
State-Changed-When: Sun Oct 22 15:04:49 PDT 2000 
State-Changed-Why:  
Superseeded by PR 21317, which has a patch for NOTES. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=10812 
>Unformatted:
