From owner-freebsd-isp  Sat Dec 21 14:45:15 1996
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA05560
          for isp-outgoing; Sat, 21 Dec 1996 14:45:15 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA05550;
          Sat, 21 Dec 1996 14:45:13 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA28229; Sat, 21 Dec 1996 15:44:52 -0700 (MST)
Date: Sat, 21 Dec 1996 15:44:52 -0700 (MST)
Message-Id: <199612212244.PAA28229@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
Cc: isp@freebsd.org, hackers@freebsd.org, petzi@apfel.de (Michael Beckmann)
Subject: Re: innd can't remalloc
In-Reply-To: <199612212156.WAA13620@uriah.heep.sax.de>
References: <Pine.BSF.3.95.961221222006.1390B-100000@server.zsb.th-darmstadt.de>
	<199612212156.WAA13620@uriah.heep.sax.de>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Next thing I'm going to upgrade to FreeBSD 2.2, to get the better malloc
> > and some other enhancements from it. The innd doesn't have to be that
> > large. I tried linking my inn with -lgnumalloc , but it was a desaster.
> 
> If the malloc is all you want, you only need to copy over
> /usr/src/lib/libc/stdlib/malloc.{3,c} from -current.  Rebuild
> your shared libc, and see whether it helped your problem.

Actually, you can't use the malloc in -current in 2.1.* since it now
uses some features that only exist in -current.  I had to grab the
pre phk/3 version which works great on my -stable systems.


Nate