Date: 20 Oct 2000 02:36:48 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Steve Ames <steve@virtual-voodoo.com> Cc: Bosko Milekic <bmilekic@dsuper.net>, freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups Message-ID: <xzp7l748i1r.fsf@flood.ping.uio.no> In-Reply-To: Steve Ames's message of "Thu, 19 Oct 2000 17:21:11 -0500" References: <200010191452.e9JEqps50765@virtual-voodoo.com> <Pine.BSF.4.21.0010191813330.27986-100000@jehovah.technokratis.com> <20001019172111.A78554@virtual-voodoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Ames <steve@virtual-voodoo.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp7l748i1r.fsf>