From: Richard Kettlewell <rjk@terraraq.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: Ben Mansell <ben@zeus.com>, Steven Dake <sdake@mvista.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Davide Libenzi <davidel@xmailserver.org>
Subject: Re: Is POLLHUP an input-only or bidirectional condition?
Date: Sat, 03 Apr 2004 13:19:30 +0100 [thread overview]
Message-ID: <848yhdz225.fsf@rjk.greenend.org.uk> (raw)
In-Reply-To: <20040402184035.GA653@mail.shareable.org> (Jamie Lokier's message of "Fri, 02 Apr 2004 18:41:59 GMT")
Jamie Lokier <jamie@shareable.org> writes:
> Perhaps that indicates some confusion over what POLLHUP is supposed to
> mean, and when it should be set by devices and/or sockets: is it for
> input hangup conditions that allow further output, or for total hangup
> conditions where input and output are both guaranteed to fail?
I spent some time a while ago looking into how various platforms treat
POLLHUP. It's rather random...
http://www.greenend.org.uk/rjk/2001/06/poll.html
--
http://www.greenend.org.uk/rjk/
next prev parent reply other threads:[~2004-04-03 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 18:25 epoll reporting events when it hasn't been asked to Ben Mansell
2004-04-01 19:28 ` Davide Libenzi
2004-04-01 23:29 ` Steven Dake
2004-04-02 9:04 ` Ben Mansell
2004-04-02 15:22 ` Davide Libenzi
2004-04-02 18:40 ` Is POLLHUP an input-only or bidirectional condition? (was: epoll reporting events when it hasn't been asked to) Jamie Lokier
2004-04-03 12:19 ` Richard Kettlewell [this message]
2004-04-03 21:44 ` Davide Libenzi
2004-04-03 22:35 ` Jamie Lokier
2004-04-04 1:28 ` Davide Libenzi
2004-04-04 2:08 ` Jamie Lokier
2004-04-04 2:49 ` Davide Libenzi
2004-04-04 18:51 ` Ben Mansell
2004-04-04 19:41 ` Davide Libenzi
2004-04-04 20:24 ` Jamie Lokier
2004-04-14 17:59 ` epoll reporting events when it hasn't been asked to Dirk Morris
2004-04-14 19:39 ` Jamie Lokier
2004-04-14 20:21 ` Dirk Morris
2004-04-14 21:48 ` Jamie Lokier
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=848yhdz225.fsf@rjk.greenend.org.uk \
--to=rjk@terraraq.org.uk \
--cc=ben@zeus.com \
--cc=davidel@xmailserver.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdake@mvista.com \
/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®