From owner-freebsd-questions Mon Dec 16 14:22:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA08682 for questions-outgoing; Mon, 16 Dec 1996 14:22:57 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts12-line3.uoregon.edu [128.223.150.135]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA08667 for ; Mon, 16 Dec 1996 14:22:48 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id OAA00519; Mon, 16 Dec 1996 14:22:35 -0800 (PST) Date: Mon, 16 Dec 1996 14:22:34 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Robert Chalmers cc: bsd Subject: Re: Does anyone from Freebsd read this group In-Reply-To: <199612132200.IAA02641@nanguo.chalmers.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, Robert Chalmers wrote: > Does anyone from FreeBSD read this posting? > > I'm still getting Malloc warnings, both from httpd, and tin. I'm still here. Again, it's not FreeBSD's fault, it's Apache's fault. It's their bug :) I think you've done this already, but contact the port's maintainer (in the port Makefile) and let them know. At least they could patch it up and send a note or fix to the Apache team. If you know how, fix it yourself and forward the patch file up. Or check out the libmalloc code and comment out the printf(). Same procedure with tin. > and write direct I guess :-) That works better. We're support, but not much migrates over, especially with ports. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major