From owner-freebsd-questions  Sat Sep 21 18:05:17 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA13655
          for questions-outgoing; Sat, 21 Sep 1996 18:05:17 -0700 (PDT)
Received: from lariat.lariat.org ([129.72.251.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA13227
          for <questions@freebsd.org>; Sat, 21 Sep 1996 18:04:19 -0700 (PDT)
Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id TAA03562 for questions@freebsd.org; Sat, 21 Sep 1996 19:03:54 -0600 (MDT)
Date: Sat, 21 Sep 1996 19:03:54 -0600 (MDT)
From: Brett Glass <brett@lariat.org>
Message-Id: <199609220103.TAA03562@lariat.lariat.org>
To: questions@freebsd.org
Subject: systat/netstat utilities buggy?
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Since I've begun to use them, the systat and netstat utilities appear
to be causing trouble in my system. netstat often returns the message

"kvm_read: Bad address"

or hangs forever. systat -netstat sometimes also hangs forever (not
always, but sometimes) and can cause odd system behavior -- as if memory
were being corrupted.

I've avoided these utilities to keep the machine from crashing, but really
need to monitor the information they provide.

Are there known problems with these programs?

--Brett