From owner-freebsd-current Wed Feb 23 12:10:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AF8DB37B9C8 for ; Wed, 23 Feb 2000 12:10:23 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA03320 for ; Wed, 23 Feb 2000 13:10:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA37081 for ; Wed, 23 Feb 2000 13:10:12 -0700 (MST) Message-Id: <200002232010.NAA37081@harmony.village.org> To: freebsd-current@freebsd.org Subject: routed dumping core? Date: Wed, 23 Feb 2000 13:10:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I go off and sink a huge amount of time into this, I was wondering if anybody else was noticing that routed in 4.0-rc2 was dumping core within a minute of the system starting. We have 4 different machines that this is hitting right now, but have not had the time to track it down any further than this. If this isn't a known problem, I'll dig further and put the time in to find/kill the bug, but I hadn't seen anything here so I thought I'd ask. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message