From owner-freebsd-current Thu Oct 19 17:37: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C75D337B4D7 for ; Thu, 19 Oct 2000 17:37:03 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA20679; Fri, 20 Oct 2000 02:36:51 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Steve Ames Cc: Bosko Milekic , freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups References: <200010191452.e9JEqps50765@virtual-voodoo.com> <20001019172111.A78554@virtual-voodoo.com> From: Dag-Erling Smorgrav Date: 20 Oct 2000 02:36:48 +0200 In-Reply-To: Steve Ames's message of "Thu, 19 Oct 2000 17:21:11 -0500" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Ames writes: > On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote: > > On Thu, 19 Oct 2000, Steve Ames wrote: > > I'm running -CURRENT from approximately 4 days ago and I am not > > noticing this. > It doesn't happen every time. But if you use the command a few times > I can almost always force a lockup. If the command is never issued the > system stays running. The sockstat(8) author does not have this problem, even though he runs sockstat(8) quite often on both -STABLE and -CURRENT systems (including bleeding-edge-hot-off-the-cvsup-server-CURRENT) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message