Date: Thu, 09 Dec 2010 02:20:39 +0200 From: Andriy Gapon <avg@freebsd.org> To: Matthew Fleming <mdf356@gmail.com> Cc: Bruce Cran <bruce@cran.org.uk>, FreeBSD-Hackers <freebsd-hackers@freebsd.org>, Chuck Robey <chuckr@telenix.org> Subject: Re: getting a list of open files versus PID nos.? Message-ID: <4D0020D7.5080706@freebsd.org> In-Reply-To: <AANLkTi==WtuJgCD7mAEJHgRer-cnzYbVyEEWAkfcsXrd@mail.gmail.com> References: <4D000448.1050606@telenix.org> <AANLkTinssm_1rPZ-pPbpGKghDbQfDx29y-y8e-NRSJHo@mail.gmail.com> <20101208230139.2097c2e8@core.draftnet> <AANLkTi==WtuJgCD7mAEJHgRer-cnzYbVyEEWAkfcsXrd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 09/12/2010 01:47 Matthew Fleming said the following: > On Wed, Dec 8, 2010 at 3:01 PM, Bruce Cran <bruce@cran.org.uk> wrote: >> On Wed, 8 Dec 2010 14:54:57 -0800 >> Matthew Fleming <mdf356@gmail.com> wrote: >> >>> This is what lsof is for. I believe there's one in ports, but I have >>> never tried it. >> >> Is there any advantage to using lsof instead of fstat(1) (fstat -p pid)? > > I believe that lsof reports on all open files by all processes, > whereas fstat will only report on a specific provided pid. Just try running fstat without any options. Or procstat -a -f. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D0020D7.5080706>