Chris Jones <[EMAIL PROTECTED]> writes:
> No, it could be any number of other things. The first that comes to
> mind is EINTR. How about something closer to:
Writes to disk files don't suffer EINTR as far as I've ever heard
(if they do, there are an awful lot of broken programs out there).
More to the point, a kernel that aborted a write because of an interrupt
*and failed to set errno* would certainly be broken. The question is
what to assume when we see that the write did not change errno.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
