I am trying to understand under the hood how the Solaris 10 Kernel routes the bytes written into one end of a unix domain socket file descriptor so that those bytes arrive at the read end of the file descriptor on the other end (another process). I would like if possible to use solaris modular debugger mdb to help understand the flow by starting at one process's end of the socket (file descriptor) and using mdb's inspection of the kernel data structures to see what the other end of the sockets Process ID (pid) and file descriptor is. Is this possible? Thanks.
↧