From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: sim@netnation.com (Simon Kirby)
Cc: linux-kernel@vger.kernel.org
Subject: Re: read() details
Date: Thu, 26 Jul 2001 23:24:28 +0100 (BST) [thread overview]
Message-ID: <E15PtYS-0004dn-00@the-village.bc.nu> (raw)
In-Reply-To: <20010726144719.A2098@netnation.com> from "Simon Kirby" at Jul 26, 2001 02:47:19 PM
> Is it safe to assume that when a single read() call of x bytes a file
> (the file being locked against other processes appending to it) returns
> less than x bytes, the next read() will always return 0? If so, is it
No. Posix allows any read to be interrupted. Unix doesn't do this. Even so
another writer in parallel on the same file will cause what you describe
next prev parent reply other threads:[~2001-07-26 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 21:47 Simon Kirby
2001-07-26 22:24 ` Alan Cox [this message]
2001-07-26 22:31 ` Simon Kirby
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=E15PtYS-0004dn-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@netnation.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®