On the silliness of close() giving EDQUOT

Richard Tobin richard at aiai.ed.ac.uk
Tue Oct 23 03:35:56 AEST 1990


In article <BZS.90Oct20172142 at world.std.com> bzs at world.std.com (Barry Shein) writes:
>I assume by NFS you mean the NFS from Sun. Writes are always
>synchronous in NFS or must appear to be (or are non-compliant and
>you're on your own.) So fsync() for writes is a no-op and irrelevant
>in that case.

The writes performed by the client kernel to the remote server must be
synchronous, so that a server crash is transparent.  Writes by the
application don't need to be synchronous - the client kernel may buffer
them - since it is not required that client crashes be transparent (:-).

-- Richard
-- 
Richard Tobin,                       JANET: R.Tobin at uk.ac.ed             
AI Applications Institute,           ARPA:  R.Tobin%uk.ac.ed at nsfnet-relay.ac.uk
Edinburgh University.                UUCP:  ...!ukc!ed.ac.uk!R.Tobin



More information about the Comp.unix.internals mailing list