From owner-freebsd-stable Sat Sep 4 22:12: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 4EAF5152FD for ; Sat, 4 Sep 1999 22:12:06 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA02378; Sat, 4 Sep 1999 22:09:24 -0700 (PDT) Message-Id: <199909050509.WAA02378@implode.root.com> To: Mike Smith Cc: Paul Saab , stable@FreeBSD.ORG Subject: Re: analyzing a crash of 3.2-RELEASE In-reply-to: Your message of "Sat, 04 Sep 1999 14:54:44 PDT." <199909042154.OAA07496@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 04 Sep 1999 22:09:24 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This looks like a race in the route handling code that was fixed a >while back; you can either disable path MTU discovery (which prevents >the massive routing table growth that you may also see in your >application) or update to 3.2-stable in which I _believe_ that this has Why would disabling PMTUD have any affect on that? The clone routes should still be created just as before. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message