Messages in this thread |  | | Date | Fri, 12 Jan 2001 16:18:28 +0100 (MET) | From | Andries.Brouwer@cwi ... | Subject | Re: O_NONBLOCK, read(), select(), NFS, Ext2, etc. |
| |
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/
|  |