From: Andries.Brouwer@cwi.nl
To: cw@f00f.org, rothwell@holly-springs.nc.us
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_NONBLOCK, read(), select(), NFS, Ext2, etc.
Date: Fri, 12 Jan 2001 16:18:28 +0100 (MET) [thread overview]
Message-ID: <UTC200101121518.QAA83968.aeb@ark.cwi.nl> (raw)
From: Chris Wedgwood <cw@f00f.org>
On Thu, Jan 11, 2001 at 09:34:08PM -0500, Michael Rothwell wrote:
The man pages for open, read and write say that if a file is opened
using the O_NONBLOCK flag, then read() and write() will always return
immediately and not block the calling process.
the man pages are wrong
Don't you think cc'ing the man page maintainer [aeb@cwi.nl]
would be a good idea whenever you think something is wrong
in the man pages? You never know, they might even improve.
In this particular case I don't think anything is actually
wrong, but I can well imagine that someone can invent clearer
wording. It would also be useful to more clearly separate
POSIX-mandated behaviour and actual Linux behaviour.
Suggestions and patches are welcome as always.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-12 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 15:18 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 18:10 O_NONBLOCK, read(), select(), NFS, Ext2, etc Dan Kegel
2001-01-12 2:34 Michael Rothwell
2001-01-12 3:28 ` Chris Wedgwood
2001-01-12 9:40 ` Alan Cox
2001-01-12 14:55 ` Michael Rothwell
2001-01-12 16:34 ` Alexander V. Lukyanov
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=UTC200101121518.QAA83968.aeb@ark.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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