Dear Gurus,
My original posting was:
> To-day, B. O'Connor sent a message stating that lsof does not indicate
> the names of the files, just the devices names.
>
> I have EXACTLY the same problem. I asked the list for help some time
> ago, but to no avail. Obviously, many colleagues here don't experience
> the problem, but many do....
Besides a dozen of "same for me", I received the following answer from Vic
Abell, the author of lsof:
> I suggest you read section 3.1 of the 00FAQ file that comes with
> the lsof distribution:
>
> 3.1 Why doesn't lsof report full path names?
>
> It will explain to you what lsof tries to do to report path names
> and why reporting full path names for all files would be too costly.
This I had already done, and I understand that lsof may not report the
full path names. What I still don't understand is why, with the same OS,
some sites get the full path names and some others don't.....
William H. Magill (magill_at_isc.upenn.edu) has no problem and kindly sent
a detailed procedure for a proper installation of lsof. I keep it for you
if you want it.
Anyway, the general consensus is to use the inode number to get the name
of the files:
---------------------
From: Keith_MCCABE_at_paribas.com (Keith MCCABE)
Use the inode number as input to the find command
find /usr -inum 1234 -exec ls -ldi {} \;
---------------------
From: System Janitor <hubcap_at_hubcap.clemson.edu>
find /partition -inum whatever
---------------------
Thanks to all of you,
Jean-Loup
--
---------------------------------------------------------------------
| Jean-Loup Risler | |
| Universite de Versailles | Tel: (33-1) 39 25 45 54 |
| Lab. Genome et Informatique | Fax: (33-1) 39 25 45 69 |
| Batiment Buffon | |
| 45 Avenue des Etats-Unis | email: risler_at_genetique.uvsq.fr |
| 78035 Versailles Cedex France | |
---------------------------------------------------------------------
Received on Tue Jan 14 1997 - 11:41:49 NZDT