On the silliness of close() giving EDQUOT

[Robert Thurlow]

In <BZS.90Oct19231046 at world.std.com> bzs at world.std.com (Barry Shein) writes:
>For a distributed file system it's harder because of the possibility
>of multiple writing processes. But writes in NFS are synchronous, so
>that's not hard, the server knows and will return the error and the
>write() doesn't return until it's committed. If you shut that off for
>performance gains you're on your own.

write(2) is not synchronous to the process; the NFS write operation is,
but they may be done later by block I/O daemon processes on your behalf
at a later time.  We allow synchronous writes, but that isn't what a
naive process gets.

#include <osi/std/disclaimer>
Rob T
--
Rob Thurlow, thurlow at convex.com or thurlow%convex.com at uxc.cso.uiuc.edu
----------------------------------------------------------------------
"This opinion was the only one available; I got here kind of late."