From owner-freebsd-hackers  Sat Oct 26 11:01:37 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA16481
          for hackers-outgoing; Sat, 26 Oct 1996 11:01:37 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16474
          for <hackers@FreeBSD.org>; Sat, 26 Oct 1996 11:01:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id KAA10225; Sat, 26 Oct 1996 10:59:52 -0700 (PDT)
Message-Id: <199610261759.KAA10225@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: jgreco@ns.sol.net
cc: hackers@FreeBSD.org
Subject: Re: HELP! :-( Hitting datasize limit 
In-reply-to: Your message of "Sat, 26 Oct 1996 09:17:14 CDT."
             <199610261417.JAA10206@earth.execpc.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 26 Oct 1996 10:59:52 -0700
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>S***!  128MB absolute datasize limit on a process?!?!
>
>This machine has 256MB RAM and if INN wants to use it all, I really do
>not care.
>
>I can probably somehow hack a "raise" to this limit myself, but I have 
>no idea what nasty side effects might be waiting for me and I am 
>wondering what the idea or architectural reasons behind this "absolute" 
>limit is.
>
>What is recommended in this case?

options "MAXDSIZ=(256UL*1024*1024)"

   ...should do the trick. I should probably make this change standard now
that large(r) memory systems are more common. 

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project