DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:x-mimeole:message-id;
        b=K8TfmCSrUSLNY/HPi3XlguXrWvtSpzsFfWl6haU7KX/8P2DKfgTY8IOLsCZdJQ6pYogHiuqB4iHzWaLe8xUnmSmquFaBjCvHMZWWATQGzwWoYWRPMMNJ6adXD2CXi2B8xK4XGmMQZlB46Aaqt9PnMv70SnUyii+ERwZKRZcYEv8=
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
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AccCDp78Q+1phDq+TvuNzHd2Ov8jFw==
Message-ID: <454fe59b.6455ade0.6506.1f45@mx.google.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 944
Lines: 24

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/