From owner-freebsd-questions Wed Sep 13 16:34:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E6D1737B423 for ; Wed, 13 Sep 2000 16:34:35 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8DNYXc25331; Wed, 13 Sep 2000 16:34:33 -0700 (PDT) Date: Wed, 13 Sep 2000 16:34:33 -0700 From: Alfred Perlstein To: cove.schneider@clearink.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Unable to use all swap? (How to up proc. memory limits?) Message-ID: <20000913163433.A12231@fw.wintelcom.net> References: <20000913124513.R79801@clearink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000913124513.R79801@clearink.com>; from cove@clearink.com on Wed, Sep 13, 2000 at 12:45:13PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Cove Schneider [000913 12:45] wrote: > Hi All, > > For some reason malloc(3) fails with an out of memory error even > though the machine has ~500MB swap left. Am I missing something > here? I'm guessing there is some setting in the config file that > I don't know about... > > Any clues/help would be greatly appreciated. See the kernel options: # Certain applications can grow to be larger than the 128M limit # that FreeBSD initially imposes. Below are some options to # allow that limit to grow to 256MB, 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. # options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message