Path: utzoo!attcan!uunet!mcsun!ukc!edcastle!aiai!richard From: richard@aiai.ed.ac.uk (Richard Tobin) Newsgroups: comp.unix.internals Subject: Re: On the silliness of close() giving EDQUOT Message-ID: <3595@skye.ed.ac.uk> Date: 22 Oct 90 17:35:56 GMT References: <1990Oct18.200939.17427@athena.mit.edu> <24048:Oct1822:23:2090@kramden.acf.nyu.edu> <9681:Oct2004:06:3090@kramden.acf.nyu.edu> Reply-To: richard@aiai.UUCP (Richard Tobin) Organization: AIAI, University of Edinburgh, Scotland Lines: 16 In article bzs@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@uk.ac.ed AI Applications Institute, ARPA: R.Tobin%uk.ac.ed@nsfnet-relay.ac.uk Edinburgh University. UUCP: ...!ukc!ed.ac.uk!R.Tobin