public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Baretta <alex@baretta.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Inadequate documentation: sockets
Date: Tue, 06 Mar 2001 20:30:46 +0100	[thread overview]
Message-ID: <3AA53AE6.5D17A6C8@baretta.com> (raw)
In-Reply-To: <200103061926.WAA23796@ms2.inr.ac.ru>

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.

      reply	other threads:[~2001-03-06 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 18:14 Inadequate documentation: sockets Alessandro Baretta
2001-03-06 18:34 ` Alan Cox
2001-03-06 17:05   ` Khalid Aziz
2001-03-06 19:26 ` kuznet
2001-03-06 19:30   ` Alessandro Baretta [this message]

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=3AA53AE6.5D17A6C8@baretta.com \
    --to=alex@baretta.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