From owner-freebsd-current Mon Jun 1 02:13:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00170 for freebsd-current-outgoing; Mon, 1 Jun 1998 02:13:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00139 for ; Mon, 1 Jun 1998 02:13:42 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA09919; Mon, 1 Jun 1998 02:12:01 -0700 (PDT) Message-Id: <199806010912.CAA09919@implode.root.com> To: John Hay cc: andrew@iaccess.com.au, freebsd-current@FreeBSD.ORG Subject: Re: mbuf cluster problem continues!! In-reply-to: Your message of "Sat, 01 Jun 1998 08:54:17 +0200." <199806010654.IAA16317@zibbi.mikom.csir.co.za> From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Jun 1998 02:12:01 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've seen several reports of mbuf leaks in the specific case of running >> squid proxy servers. As I don't have anything remotely resembling that in any >> configuration I have here, someone else will have to troubleshoot this one. >> It's possible that this might actually be a bug in squid rather than in >> FreeBSD. I have really no idea; I've not seen any mbuf leaks in any other >> networking use of FreeBSD so it is surprising that one would show up when >> doing this. > >Isn't it just the various TCP wait states for old connections that still >have to timeout that look like mbuf leaks? Even on my not-so-very-busy >squid server there is always some of them hanging around. You can easily >see that with "netstat -an". That could be...certainly something to check out. I seem to recall that the previous report of this problem was with a machine that had a very light proxy load, so it seemed unlikely that old connections could be a serious problem. ...but perhaps either the load wasn't as light as thought or perhaps there were very few mbuf clusters configured (or both). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message