From: "Dr. Werner Fink" <werner-l3A5Bk7waGM@public.gmane.org>
To: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Inode for netlinks in /proc/net/netlink?
Date: Tue, 27 Jan 2009 15:41:56 +0100 [thread overview]
Message-ID: <20090127144156.GA30646@boole.suse.de> (raw)
Hi,
currently (2.6.27) there seems to be no Inode informations about
the existing netlinks, only the pid of the process who has opened
such a netlink is seen. Nevertheless, the file descriptor is
passed over to the child of the creator, e.g. after a fork for
a user space daemon like udevd.
Is there any other way to determine which socket found in dir
/proc/<pid>/fd/ is a netlink and also to determine which type
of netlink it is? The lsof utility reports
can't identify protocol
for such netlinks.
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2009-01-27 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090127144156.GA30646@boole.suse.de \
--to=werner-l3a5bk7wagm@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).