Date: Tue, 14 May 2002 10:55:14 -0400 From: "Galella, Anthony" <anthony.galella@intel.com> To: "'Andrew'" <andrew@ugh.net.au>, "Galella, Anthony" <anthony.galella@intel.com> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: RE: esd/esound? was: How can I clear out these netstat messages ? Message-ID: <59F55CE047A6D51196360002A534A4AC370467@pysmsx102.py.intel.com>
next in thread | raw e-mail | index | archive | help
Hhmmmm. Nope. sockstat doesn't help, These are listed as Active Unix sockets, they have an address next to them, not a port number. An interesting note though, if I do an fstat on any one of those socket addresses in question, I get the following: bash-2.05a$ fstat -mv | grep d7fe8980 can't read vnode at 0x0 for pid 6 can't read vnode at 0x0 for pid 5 can't read vnode at 0x0 for pid 4 can't read vnode at 0x0 for pid 3 can't read vnode at 0x0 for pid 2 can't read vnode at 0x0 for pid 0 I tried doing a kill -HUP on pids 0 through 6, but no help. -----Original Message----- From: Andrew [mailto:andrew@ugh.net.au] Sent: Monday, May 13, 2002 7:33 PM To: Galella, Anthony Cc: 'freebsd-questions@freebsd.org' Subject: Re: esd/esound? was: How can I clear out these netstat messages? On Mon, 13 May 2002, Galella, Anthony wrote: > My concern is that the Active Unix sockets are "hung" (I don't even know how > the esd calls got initiated) sockstat will tell you the PID that has the socket open. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59F55CE047A6D51196360002A534A4AC370467>