*BSD News Article 76364


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.hawaii.edu!news.uoregon.edu!vixen.cso.uiuc.edu!uwm.edu!cs.utexas.edu!academ!bcm.tmc.edu!pendragon!news.jsc.nasa.gov!mozo.cc.purdue.edu!vic.cc.purdue.edu!abe
From: abe@vic.cc.purdue.edu (Vic Abell)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: lsof and OpenBSD [was Re: List of OpenBSD change]
Date: 18 Aug 1996 13:38:18 GMT
Organization: Purdue University
Lines: 45
Message-ID: <4v76ca$6c0@mozo.cc.purdue.edu>
References: <DERAADT.96Aug8144209@zeus.theos.com> <DERAADT.96Aug17013749@zeus.theos.com>
NNTP-Posting-Host: vic.cc.purdue.edu

In article <DERAADT.96Aug17013749@zeus.theos.com> deraadt@theos.com (Theo de Raadt) writes:
>
>    `lsof'-style features in fstat.

Unless I misunderstood the email that Theo and I exchanged about
including lsof in the Open BSD distribution, he added exactly one
lsof feature to OpenBSD's fuser: the ability to report local and
foreign addresses on open socket files.  What I think he added
might more accurately  be called an SGI IRIX fuser feature.

Lsof's main feature is that it runs on many different UNIX dialects
and offers the same command interface and output on all.  That's
a hard feature to incorporate in a dialect-limited command like
OpenBSD's fuser.

Other lsof features that may not be in OpenBSD's fuser include
output that can easily be parsed by subsequent filters -- e.g.,
AWK and Perl scripts; a wide range of search specifications,
including the ability to get reports on open socket files of a
specific protocol, network address, service name range, or port
name range; device cacheing for improved performance; reporting of
text file segments and loader files in use by a process; probing
the kernel namne cache for path names of open files; and so on.

I don't currently offer an OpenBSD port, because I don't have a
test system.  If anyone can provide one (Theo declined.), I would
be glad to investigate the effort required.

As I understand it, Theo is reluctant to add lsof to the OpenBSD
distribution because of the size of its source tree -- about 600KB
in gzip'd tar archive form.  Of course, that includes source for
many UNIX dialects and their variants, plus extensive documentation.
A single dialect source tree with minimum documentation takes about
100KB in gzip'd form.

Lsof is freely available from:

	ftp://vic.cc.purdue.edu/pub/tools/unix/lsof

Lsof currently supports AIX, BSDI, CDC EP/IX, FreeBSD, HP-UX, Linux,
NetBSD, NeXTSTEP, DEC OSF/1 (Digital UNIX), Sequent PTX, MIPS
RISCos, SCO UNIX, SGI IRIX, Solaris 2.x  and SunOS 4.1.x, and
Ultrix.

Vic Abell, lsof author <abe@purdue.edu>