checking close's return value

[Daryl Monge]

In article <1213 at unmvax.unm.edu> mike at turing.unm.edu (Michael I. Bushnell) writes:
>UNIX does *not* guarantee that hardware related errors
>will get reflected on write.  This is one of its deficiencies, but is
>unavoidable given the implementation of the filesystem.  The actual
>disk write may take place hours after the write(2) system call
>(assuming update isn't running).

So true.  I would like it if close(2) would insure all blocks were
successfully written to disk before it returned.
(Possibly by an fcntl(2) option if every one doesn't want this?)

Daryl Monge				UUCP:	...!att!ihcae!daryl
AT&T					CIS:	72717,65
Bell Labs, Naperville, Ill		AT&T	312-979-3603