Message-ID: <3AA53AE6.5D17A6C8@baretta.com>
Date: Tue, 06 Mar 2001 20:30:46 +0100
From: Alessandro Baretta <alex@baretta.com>
MIME-Version: 1.0
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Inadequate documentation: sockets
In-Reply-To: <200103061926.WAA23796@ms2.inr.ac.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

kuznet@ms2.inr.ac.ru wrote:
> 
> Hello!
> 
> > The manual specifies the following flag to be returned by the
> > kernel
> > [smip]
> 
> The information is is not quite correct.
> [snip]

The information you gave me sounds interesting, but it is conflict
with the documentation. This was my original assertion: the
documentation on the subject is inadequate.

> > Finally I'm left with my original problem: how am I supposed to
> > detect a close or a shutdown from the peer?
> 
> By EOF. No other way exists. POLLHUP is local condition, only
> local side can close connection in write direction. Exception
> is abort (reset) initiated by peer.

What do you mean by "local condition"? You surely do not mean that
the event which provokes the POLLHUP occours on my host? What
about a shutdown(sock, SHUT_RD) called by the peer?

> > by addressing me to more adequate documentation.
> 
> UNIX98 and Austin draft pages. The are very ambiguous though.
> 
Hmmmm....

Thank you very much!

Alex

P.S. Alexey, I meant this post to be for the list. The copy I sent
to you privately is my mistake.
-
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/