=Start=<\/p>\n
\u6211\u77e5\u9053\u5728Linux\u4e0b\u5982\u4f55\u901a\u8fc7pid\u627e\u5230\u5bf9\u5e94\u7684inode\u4fe1\u606f\uff0c\u4f46\u662f\u73b0\u5728\u6709\u4e00\u4e2a\u9700\u6c42\u5c31\u662f\u901a\u8fc7inode\u627e\u5230\u5bf9\u5e94\u7684pid\u3002<\/p>\n
In general, to find what’s at the other end of a socket, you need to\u00a0iterate through \/proc<\/span>.<\/strong>\u00a0This can of course mean letting an existing tool such as netstat, lsof or ss do it for you.<\/p>\n The reason for this is that a socket can be opened by different processes.<\/strong><\/span>\u00a0Once a process has opened a socket, it can fork, and the children can change their privileges and switch to different namespaces. It’s also possible to pass file descriptors from a process to an unrelated process, using anciliary data on a unix socket.\u00a0So arbitrary processes can have the same socket open.<\/span>\u00a0There is no such thing as \u201cthe PID of a socket\u201d, only \u201cthe PIDs of a socket\u201d.<\/p>\n While this doesn’t prove that there’s no way to enumerate the PIDs given the socket, it would be very difficult to design such an interface, especially when you consider that non-root users don’t get to know when files are opened by processes running as a different user. Access through \/proc enforces security via permissions, and I’m not aware of any other interface to get the same data. Also, fuser, lsof, netstat and ss all enumerate \/proc; if there was another interface, I’d expect someone to use it.\u00a0So I’m pretty sure that there’s no other way.<\/strong><\/span><\/p>\n <\/p>\n https:\/\/unix.stackexchange.com\/questions\/302152\/is-there-a-way-to-identify-the-pid-or-cgroup-of-a-socket-without-iterating-thr<\/a><\/p>\n https:\/\/stackoverflow.com\/questions\/3319521\/how-can-i-match-each-proc-net-tcp-entry-to-each-opened-socket\/<\/a><\/p>\n https:\/\/stackoverflow.com\/questions\/14667215\/finding-a-process-id-given-a-socket-and-inode-in-python-3<\/a><\/p>\n\u53c2\u8003\u94fe\u63a5\uff1a<\/h5>\n