Date: Tue, 7 Nov 2000 17:26:16 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Polstra <jdp@polstra.com> Cc: des@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Is sockstat broken in -stable? Message-ID: <14856.28717.596196.163734@grasshopper.cs.duke.edu> In-Reply-To: <XFMail.001107091801.jdp@polstra.com> References: <XFMail.001107091801.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra writes: > On a -stable system from October 31, I'm seeing this from sockstat: > > alpha$ sockstat > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS > root sshd 13195 5 ? ? ? <..> > Userland and kernel are in sync. This is on an Alpha, though I > don't know whether that's significant or not. Is anybody else > seeing this problem? This is alpha (aka 64-bit) specific. There are 2 problems. The first is that fstat is borked. It is casting addresses to ints and printing out 8 fields rather than 16: root sshd1 714 5* internet stream tcp 63e9200 ............................................................^^^^^^^^ The second is that this netstat is not borked. Its printing out all 16 fields of addresses on alpha: fffffe00063e9200 tcp4 0 20 thunder.ssh grasshopper.998 ESTABLISHED ........^^^^^^^^^^^^^^^^^ Between the 2, sockstat cannot match things up. Eg, 0xfffffe00063e9200 != 0x63e9200 Changing the width of the netstat match to 16 helps a little, but because of the fstat problem, its not enough. This could probably be patched up by stream-editing netstat's output so as to chop off the high 8 fields of addresses coming from netstat. Dag? It would be far better to fix fstat.. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14856.28717.596196.163734>