1

Topic: Unix sockets: self connection

What for? I would understand cross-joints - to track death of process. But here, judging by netstat, process is connected to the socket. The second question about 4 not clear connections for which except inode anything is not present. How to receive them endpoint? Tried "busybox find-inum NN" on inode. For/dev finds nothing. Without instructions of a way the output is volume, but there is nothing with a word socket. Linux kernel version: 3.4.67 : untitled connections it is visible only from under root. unix 2 [ACC] STREAM LISTENING 843 302/360sguard/dev/socket/360smonitorxx1 unix 2 [ACC] STREAM LISTENING 1528 299/360sguard/dev/socket/360smonitorxx2 unix 3 [] STREAM CONNECTED 1531 302/360sguard unix 3 [] STREAM CONNECTED 845 299/360sguard/dev/socket/360smonitorxx2 unix 3 [] STREAM CONNECTED 847 302/360sguard unix 3 [] STREAM CONNECTED 846 299/360sguard unix 3 [] STREAM CONNECTED 848 302/360sguard/dev/socket/360smonitorxx1 unix 3 [] STREAM CONNECTED 1530 299/360sguard shell@P172R10:/$ ps | grep 360s root 299 1 7452 128 ffffffff 00000000 S 360sguard root 302 1 7452 128 ffffffff 00000000 S 360sguard

2

Re: Unix sockets: self connection

Hello, IID, you wrote: IID> I would understand cross-joints - to track death of process. But here, judging by netstat, process is connected to the socket. signal pipe through socketpair? Though it  style. IID> the second question about 4 not clear connections for which except inode anything is not present. How to receive them endpoint? http://unix.stackexchange.com/questions/16300/