From: "Bin Chen" <binary.chen@gmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: UNIX domain socket problem
Date: Tue, 7 Nov 2006 09:47:02 +0800 [thread overview]
Message-ID: <454fe59b.6455ade0.6506.1f45@mx.google.com> (raw)
Sorry for cross post, it has been posted on
comp.os.linux.development.apps.
I wrote a domain socket sever, which is a STREAM type, let it listen a
sun_path, and in a while loop it accept new connections. I analyze it
using netstat.
Abstractly, the communication need two end. Even the listen socket is
only one, each time the accept returns, there should be two end
produced: one by connect() issued by client, one by accept() issued by
server. These two should have different inode number.
What is strange is that I sometimes find the RefCnt of some unix domain
socket have values 2,3,4,5,6,7 or even 258, if each connection in
stream should be in pair, why this problem occurs?
Thanks.
Binary
next reply other threads:[~2006-11-07 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 1:47 Bin Chen [this message]
2006-11-07 10:23 ` Bernd Petrovitsch
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=454fe59b.6455ade0.6506.1f45@mx.google.com \
--to=binary.chen@gmail.com \
--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
all inboxes | Powered by JetHome®