From owner-freebsd-current  Sat Mar 25 12:11:10 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 9670737B93B
	for <freebsd-current@FreeBSD.ORG>; Sat, 25 Mar 2000 12:11:08 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA04706;
	Sat, 25 Mar 2000 12:11:50 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Arun Sharma <adsharma@sharmas.dhs.org>
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	FreeBSD Current <freebsd-current@FreeBSD.ORG>
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 12:11:50 -0800
Message-ID: <4703.954015110@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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 ?

It's purely an optional file; one doesn't need to be installed by
default in order for things to behave as expected.  Consider it
a debugging feature.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message