From owner-freebsd-hackers  Wed Nov 13 10:38:03 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA04850
          for hackers-outgoing; Wed, 13 Nov 1996 10:38:03 -0800 (PST)
Received: from dyson.iquest.net ([198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA04843
          for <hackers@FreeBSD.ORG>; Wed, 13 Nov 1996 10:37:51 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id NAA00686; Wed, 13 Nov 1996 13:37:44 -0500 (EST)
From: John Dyson <dyson@dyson.iquest.net>
Message-Id: <199611131837.NAA00686@dyson.iquest.net>
Subject: Re: Setting maximum RAM consumption by a process
To: karl@Mcs.Net (Karl Denninger)
Date: Wed, 13 Nov 1996 13:37:39 -0500 (EST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199611131808.MAA15951@Jupiter.Mcs.Net> from "Karl Denninger" at Nov 13, 96 12:08:48 pm
Reply-To: dyson@FreeBSD.ORG
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Hi folks,
> 
> I know how to do this for BSDI (maximum segment size) but not for FreeBSD,
> and the same parameters don't appear to work.
> 
> Basically, our news server is now reaching a WSS of 100MB+, and we need to
> increase it (because we're getting malloc failures and death of the process
> :-)
> 
> The system has lots of RAM, so that's not a problem.
> 
> Anyone got the magic words for the config file?
> 
You can set it dynamically with ulimit (up it to 128M.)  Any further,
you can set the config variables DFLDSIZ and MAXDSIZ to practically
anything you want.  So, for 192MB

options "MAXDSIZ=201326592"
options "DFLDSIZ=201326592"

John