Date: Tue, 21 May 2002 01:11:56 +0300 (IDT) From: Roman Shterenzon <roman@xpert.com> To: Vic Abell <abe@vic.cc.purdue.edu> Cc: <freebsd-stable@freebsd.org> Subject: Re: lsof: no socket type Message-ID: <Pine.GSO.4.33.0205210108560.18600-100000@techst02.technion.ac.il> In-Reply-To: <200205202030.g4KKULd09690@vic.cc.purdue.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Seems that it's my fault, I built world on Apr 26, and I rebuilt kernel after May 1st, after /usr/include/sys/socketvar.h was updated. Sorry for the trouble. On Mon, 20 May 2002, Vic Abell wrote: > Roman, > > Via a Google search I can across this posting to sol.lists.freebsd.stable: > > > > Hello, > > > > In the latest builds lsof produces "no socket type" for all kinds of > > sockets. > > > > Can anyone reproduce this problem? Is it a problem with lsof or FreeBSD? > > > > --Roman > > This is probably the result of a mis-match between the definition > of the socket structure with which the kernel was built and the > definition of the socket structure with which lsof was built. (The > socket structure for building lsof comes from <sys/socketvar.h>.) > > I'm not sure of the state of the one 4.5-STABLE test host available > to me, so I'm going to have to send some e-mail to its administrator > to determine its state. Then I might be able to tell you if I can > reproduce your problem. > > The answer to your second question may be that it is a FreeBSD > problem or it is a header file synchronization problem on your > system. I don't think it is an lsof problem. > > If I learn more about this, I'll send you an update. > > Vic Abell, lsof author > 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?Pine.GSO.4.33.0205210108560.18600-100000>