From owner-freebsd-current Sat Mar 25 12: 5:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D91ED37B74F for ; Sat, 25 Mar 2000 12:05:22 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA00774; Sat, 25 Mar 2000 21:05:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Arun Sharma Cc: FreeBSD Current Subject: Re: malloc.conf In-reply-to: Your message of "Sat, 25 Mar 2000 12:01:59 PST." <20000325120159.A10568@sharmas.dhs.org> Date: Sat, 25 Mar 2000 21:05:18 +0100 Message-ID: <772.954014718@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000325120159.A10568@sharmas.dhs.org>, Arun Sharma writes: >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote: >> >> Please read the malloc(3) manual page. >> > >I did and created malloc.conf as documented there. And things were >fine after that. Wouldn't it be better if the build process created >a default /etc/malloc.conf ? Exactly how did you create it ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message