From owner-freebsd-stable Mon May 20 15:12:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from techst02.technion.ac.il (techst02.technion.ac.il [132.68.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 9509537B407 for ; Mon, 20 May 2002 15:11:59 -0700 (PDT) Received: by techst02.technion.ac.il (Postfix, from userid 11469) id 37A1F14C89; Tue, 21 May 2002 01:11:57 +0300 (IDT) Received: from localhost (localhost [127.0.0.1]) by techst02.technion.ac.il (Postfix) with ESMTP id 2F4D311E37; Tue, 21 May 2002 01:11:57 +0300 (IDT) Date: Tue, 21 May 2002 01:11:56 +0300 (IDT) From: Roman Shterenzon X-X-Sender: To: Vic Abell Cc: Subject: Re: lsof: no socket type In-Reply-To: <200205202030.g4KKULd09690@vic.cc.purdue.edu> Message-ID: Organization: Xpert UNIX Systems Ltd. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 .) > > 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