Date: Sat, 21 Dec 1996 15:44:52 -0700 (MST) 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 Message-ID: <199612212244.PAA28229@rocky.mt.sri.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612212244.PAA28229>