From owner-freebsd-bugs Fri Jul 7 00:44:40 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA03337 for bugs-outgoing; Fri, 7 Jul 1995 00:44:40 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA03331 for ; Fri, 7 Jul 1995 00:44:39 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id AAA02088; Fri, 7 Jul 1995 00:44:25 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id AAA01595; Fri, 7 Jul 1995 00:45:07 -0700 Message-Id: <199507070745.AAA01595@corbin.Root.COM> To: "Kenneth D. Merry" cc: freebsd-bugs@freebsd.org Subject: Re: strange netstat errors In-reply-to: Your message of "Fri, 07 Jul 95 03:38:08 EDT." <199507070738.DAA24977@rflab1.gtri.gatech.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 07 Jul 1995 00:45:07 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk > I've been getting occasional strange error messages from netstat, >usually something like this: (this is under 2.0.5) > >---- >Active Internet connections >Proto Recv-Q Send-Q Local Address Foreign Address (state) >tcp 0 0 wc206.auth wc115.1123 TIME_WAIT >netstat: kvm_read: kvm_read: Bad address This can happen whenever the internal state of the kernel changes while the information is being read. It can be made somewhat more robust and I might take a stab at it before 2.1R. -DG