When I do: ls -lsa /proc/<pid>/fd
I often see fds open on pipes, and the notation is like:
3 -> pipe:[123456]
where 123456 is a sequence of usually between 6 and 8 digits. My question >is: To what does this number map? What does it mean?
gazelle@shell.xmission.com (Kenny McCormack) writes:
When I do: ls -lsa /proc/<pid>/fd
I often see fds open on pipes, and the notation is like:
3 -> pipe:[123456]
where 123456 is a sequence of usually between 6 and 8 digits. My question >>is: To what does this number map? What does it mean?
First guess, the pid of the process on the other side of the pipe (which
may be the same process or a child process).
type:[inode]
For example, socket:[2248868] will be a socket and its
inode is 2248868. For sockets, that inode can be used to
find more information in one of the files under
/proc/net/.
HTH
In article <yga8rzw4e9b.fsf@akutech.de>, Ralf Fassel <ralfixx@gmx.de> wrote: ...
type:[inode]
For example, socket:[2248868] will be a socket and its
inode is 2248868. For sockets, that inode can be used to
find more information in one of the files under
/proc/net/.
HTH
It pretty much tells me things I already knew.
What I'm looking for is "What can I do with this number?" You say it is an "inode" number, but I doubt it is matches to a file in the file system.
I.e., you would do: find / -inum 123456 -ls
Longer term, what I am really looking for is "Who is on the other end of
this pipe?"
First guess, the pid of the process on the other side of the pipe
In article <yga8rzw4e9b.fsf@akutech.de>, Ralf Fassel <ralfixx@gmx.de> wrote:
type:[inode]
For example, socket:[2248868] will be a socket and its
inode is 2248868. For sockets, that inode can be used to
find more information in one of the files under
/proc/net/.
HTH
It pretty much tells me things I already knew.
What I'm looking for is "What can I do with this number?" You say it
is an "inode" number, but I doubt it is matches to a file in the file
system. I.e., you would do: find / -inum 123456 -ls
Longer term, what I am really looking for is "Who is on the other end
of this pipe?"
with <shvvnv$2667d$1@news.xmission.com> Kenny McCormack wrote:
In article <yga8rzw4e9b.fsf@akutech.de>, Ralf Fassel <ralfixx@gmx.de> wrote:
type:[inode]
For example, socket:[2248868] will be a socket and its
inode is 2248868. For sockets, that inode can be used to
find more information in one of the files under
/proc/net/.
HTH
It pretty much tells me things I already knew.
What I'm looking for is "What can I do with this number?" You say it
is an "inode" number, but I doubt it is matches to a file in the file
system. I.e., you would do: find / -inum 123456 -ls
Longer term, what I am really looking for is "Who is on the other end
of this pipe?"
If it's listening, then probably nothing. Anyway, quick grep through
'man lsof' suggests '/proc/net/unix'.
In article <yga8rzw4e9b.fsf@akutech.de>, Ralf Fassel <ralfixx@gmx.de> wrote: ...
type:[inode]
For example, socket:[2248868] will be a socket and its
inode is 2248868. For sockets, that inode can be used to
find more information in one of the files under
/proc/net/.
HTH
It pretty much tells me things I already knew.
What I'm looking for is "What can I do with this number?" You say it is an "inode" number, but I doubt it is matches to a file in the file system.
I.e., you would do: find / -inum 123456 -ls
Longer term, what I am really looking for is "Who is on the other end of
this pipe?"
Eric Pozharski <whynot@pozharski.name> writes:
with <shvvnv$2667d$1@news.xmission.com> Kenny McCormack wrote:
In article <yga8rzw4e9b.fsf@akutech.de>, Ralf Fassel
<ralfixx@gmx.de> wrote:
A pipe is not a UNIX domain socket (listed in /proc/net/unix).If it's listening, then probably nothing. Anyway, quick grep throughFor example, socket:[2248868] will be a socket and itsIt pretty much tells me things I already knew.
inode is 2248868. For sockets, that inode can be used to >>>> find more information in one of the files under
/proc/net/.
What I'm looking for is "What can I do with this number?" You say
it is an "inode" number, but I doubt it is matches to a file in the
file system. I.e., you would do: find / -inum 123456 -ls
Longer term, what I am really looking for is "Who is on the other
end of this pipe?"
'man lsof' suggests '/proc/net/unix'.
Longer term, what I am really looking for is "Who is on the other end of
this pipe?"
Assuming you know the inode number, lsof | grep <inode number> will tell
you that (ls -l /prroc/*/fd | grep ...).
Sorry, but I don't think you will be able to answer that question directly.
IDK, but you /might/ be able to explicitly mount pipefs to some part of the >filesystem tree. I can't guarantee that this will work, nor can I speculate >on /if/ any userland utility would be able to access it to provide you with >the information you seek.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 64:21:44 |
Calls: | 6,488 |
Calls today: | 1 |
Files: | 12,096 |
Messages: | 5,274,794 |