read() and EOF

The linux man pages say that read() returns a 0 at end of file. Is there a guarantee that it will continue to do that on subsequent read() from the same fd, or is it conformant to return a 0 once, and then an error after that? (I vaguely recall seeing that there are situations where EOF is only returned once, but I could be mistaken.)

Thanks,

David Mathog
.

Relevant Pages

  • Re: OT: Letter to TigerDirect
    ... > want to know if a particular product is Linux compatible. ... Then you find out the problem: When you slap a sticker on hardware ... suppliers who *also* guarantee the hardware with that OS, ...
    (Debian-User)
  • Re: What blocks a write to a socket pair?
    ... Linux, apparently, guarantees in-order reliable delivery of ... SOCK_DGRAM packets over a unix domain socket. ... bizarre to guarantee they're reliable and not guarantee they're ... with Linux they are not documenting ...
    (comp.unix.programmer)
  • Re: Dissing newbies from "nunya", was Re: mount: /dev/cdrom is not a valid block device
    ... Guessing has no place in a technical group. ... Who are you to "guarantee that what YOU know about Linux would fit in one ...
    (comp.os.linux.setup)
  • Re: Historical question
    ... > wouldn't in a secure shell script for example, java no longer works. ... Much like linux, FreeBSD's QA goes through the userbase. ... This is not a guarantee that it will be fixed overnight, ...
    (comp.unix.bsd.freebsd.misc)
  • Re: novell-suse linux dead meat?
    ... >> guarantee that it's going to work with your hardware. ... The vast majority of Linux software will work on any hardware ...
    (alt.os.linux.suse)