On 29/12/06, Zhasper <[EMAIL PROTECTED]> wrote:
From the lsof man page:
> An open file may be a regular file, a directory, a block special file, a
character special file, an
> executing text reference, a library, a stream or a network file
(Internet socket, NFS file or UNIX
> domain socket.)
That ("Internet socket") is lsof-specific definition.
How are you defining "file"?
Would "something that can be named using a UNIX path and can be opened with
open(2)" (i.e. not directories) satisfy you?
UNIX-domain sockets, which are usually uninteresting, indeed occupy
i-nodes
> on filesystems, but I'm not aware of a standard way to map network
sockets (
> e.g. TCP/UDP sockets) to filesystem names. Do you? (maybe there is some
> specialized linux filesystem which does this, but I don't see one on my
> system right now.
I thought there might be something in /proc, but I can't see anything.
Me too. Tried to look around /proc, /dev and even /sys after your first
reply but couldn't see anything except for /proc/net/{tcp,udp}, which don't
really count do they (look like the source for netstat(8) output) ?
Cheers, and Happy New Year
--P
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
