Date: Wed, 8 Dec 2010 15:47:18 -0800 From: Matthew Fleming <mdf356@gmail.com> To: Bruce Cran <bruce@cran.org.uk> Cc: FreeBSD-Hackers <freebsd-hackers@freebsd.org>, Chuck Robey <chuckr@telenix.org> Subject: Re: getting a list of open files versus PID nos.? Message-ID: <AANLkTi==WtuJgCD7mAEJHgRer-cnzYbVyEEWAkfcsXrd@mail.gmail.com> In-Reply-To: <20101208230139.2097c2e8@core.draftnet> References: <4D000448.1050606@telenix.org> <AANLkTinssm_1rPZ-pPbpGKghDbQfDx29y-y8e-NRSJHo@mail.gmail.com> <20101208230139.2097c2e8@core.draftnet>
next in thread | previous in thread | raw e-mail | index | archive | help
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. =A0I 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. Thanks, matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi==WtuJgCD7mAEJHgRer-cnzYbVyEEWAkfcsXrd>