public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Stelmach <stlman@poczta.fm>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Łukasz Stelmach" <stlman@poczta.fm>
Subject: unix socket connection tracking
Date: Fri, 21 Apr 2006 00:31:53 +0200	[thread overview]
Message-ID: <44480BD9.5080100@poczta.fm> (raw)

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

Greetings All.

I feel dumb as never so please enlight me. Is ther a way to find out which
process is on the other end of a unix socket pointed by a specified fd in a process.

Lets say that I have got a process gconfd-2. I've straced it and got:

writev(25, [{"GIOP\1\2\1\0\267\1\0\0", 12},....

now I look at lsof
COMMAND     PID     USER   FD   TYPE     DEVICE SIZE  NODE NAME
gconfd-2   2282 jdoe       25u  unix 0xc55a9380       4222 socket

and netstat

Proto RefCnt Flags       Type       State         I-Node PID/Program name  Path
unix  3      [ ]         STREAM     CONNECTED     4222     2282/gconfd-2

OK, fine when the gconfd-2 has written the data something's had to read it. I
ask: How can I find what has read the data? Forgive me if it's trivial but I
really find no way to learn it. Neither in /proc nor using some tools like above.

Best regards.
PS. please don't forget to CC.
-- 
Było mi bardzo miło.                    Czwarta pospolita klęska, [...]
>Łukasz<                      Już nie katolicka lecz złodziejska.  (c)PP


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

             reply	other threads:[~2006-04-20 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 22:31 Lukasz Stelmach [this message]
2006-04-21 12:53 ` unix socket connection tracking Jan Engelhardt
2006-04-21 13:35   ` Lukasz Stelmach
2006-04-21 14:12     ` Jan Engelhardt
     [not found]       ` <444A1B86.1060701@poczta.fm>
2006-04-22 13:34         ` Jan Engelhardt
2006-04-23  9:37           ` Lukasz Stelmach
2006-04-23 17:38             ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44480BD9.5080100@poczta.fm \
    --to=stlman@poczta.fm \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox