I agree with you, however I think Itai did highlight an interesting point
there. I confess that I missed that first EOVERFLOW case (whilst Itai
clearly missed the last one - so we are even :) ).
More to the point, the first case of EOVERFLOW:
The file is a regular file, nbyte is greater than 0, the starting
position is before the end-of-file and the starting position is
greater than or equal to the offset maximum established in the open
file description associated with fildes.
I am starting to think that this "offset maximum" is really RLIMIT_FSIZE
(see getrlimit(2)) because there is a provision for the starting position
to be before the end of file and at the same time greater than or equal to
the "offset maximum".
But, yes, what I said originally about pread() not setting errno=EOVERFLOW
when it should, remains correct.
Regards,
------
Tigran A. Aivazian | http://www.sco.com
Escalations Research Group | tel: +44-(0)1923-813796
Santa Cruz Operation Ltd | http://www.aivazian.demon.co.uk
On Tue, 26 Jan 1999, Matti Aarnio wrote:
> A few more lines down where the pread() special cases are
> described. Read the ENTIRE document before uttering something
> which tells you didn't read it all.
>
> These are, after all, ``man pages'' which requires certain
> reading style. POSIX standards are a bit more obscure, though,
> and require even more convoluted reading styles.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/