From owner-freebsd-stable Thu Dec 9 10:10:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2027614D0D for ; Thu, 9 Dec 1999 10:10:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA29559; Thu, 9 Dec 1999 10:10:23 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA37991; Thu, 9 Dec 1999 10:10:22 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 9 Dec 1999 10:10:22 -0800 (PST) Message-Id: <199912091810.KAA37991@vashon.polstra.com> To: blk@skynet.be Subject: Re: Route table leaks In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brad Knowles wrote: > > Kernel is rebuilt and the machine has come back up. I've got a > script running to monitor the leakage. However, I obviously haven't > been running very long, and there's been no chance to see the leak. > Do you have any suggestion on how I can try to force some leakage? Yep, but I don't want to taint the results since I'm interested in finding out whether it fixes _your_ leaks, not mine. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message