From owner-freebsd-hackers  Sat Oct 26 08:34:49 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA02335
          for hackers-outgoing; Sat, 26 Oct 1996 08:34:49 -0700 (PDT)
Received: from critter.tfs.com (disn9.cybercity.dk [194.16.57.9])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02327;
          Sat, 26 Oct 1996 08:34:42 -0700 (PDT)
Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id RAA17121; Sat, 26 Oct 1996 17:34:58 +0200 (MET DST)
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> 
Date: Sat, 26 Oct 1996 17:34:58 +0200
Message-ID: <17119.846344098@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199610261417.JAA10206@earth.execpc.com>, Joe Greco writes:

>It starts off executing at about 55MB and will generally grow to double
>that within 12 hours.  However, lately, it has been dying multiple times
>daily with malloc errors (using phkmalloc, but given the apparent cause
>I do not think this is the problem).  The current situation would tend 
>to have caused it to grow >> 110MB... and when I did a little looking
>into the problem, malloc was indeed returning NULL, which caused me to
>scratch my head until I typed "unlimit; limit"...

You may want to

	ln -sf H /etc/malloc.conf

I've not gotten a complete picture, but people indicate that it helps
a little bit.

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Future will arrive by its own means, progress not so.