Date: Wed, 07 Jun 2006 02:04:43 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-stable@freebsd.org, "Eduardo Meyer" <dudu.meyer@gmail.com> Subject: Re: How can I know which files a proccess is accessing? Message-ID: <m3lks9omp0.fsf@merlin.emma.line.org> In-Reply-To: <d3ea75b30606061416i60630419k9505b076edd2f4c7@mail.gmail.com> (Eduardo Meyer's message of "Tue, 6 Jun 2006 18:16:39 -0300") References: <d3ea75b30606061339u55efbecemab0d3d0eb9adb636@mail.gmail.com> <20060606211327.GG32476@bunrab.catwhisker.org> <d3ea75b30606061416i60630419k9505b076edd2f4c7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Eduardo Meyer" <dudu.meyer@gmail.com> writes: > On 6/6/06, David Wolfskill <david@catwhisker.org> wrote: >> You may find the "lsof" port useful for answering such questions. >> > > I tried it, but it seems that I found some limitations: > > lsof: no local file space at PID 16543 > > # ps 16543 > PID TT STAT TIME COMMAND > 16543 ?? S 0:02.43 /usr/local/sbin/httpd -k start -DSSL > > Any tuning would do the job? Are you running with tightened up security that might prevent fstat from accessing /dev/kmem? I don't know fstat failures from experience or what causes it to just show inode numbers - perhaps delete files that are still open. I'm unsure about the reason for lsof's complaint; if you installed a package, try rebuilding the port. Something different, if fstat and lsof continue to fail: you may try attaching a syscall tracer such as truss, ktrace or strace (the latter from ports) to the process and see if it leaks file descriptors. This may fail due to permissions however. -- Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3lks9omp0.fsf>