Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!llustig!objy!prefect!peter
From: peter@prefect.Berkeley.EDU (Peter Moore)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS writes and fsync().
Message-ID: <1990Oct16.085057.16691@objy.com>
Date: 16 Oct 90 08:50:57 GMT
References: <1990Oct9.152612@objy.objy.com> <thurlow.655748135@convex.convex.com> <1990Oct14.082712.10811@objy.com> <thurlow.655915475@convex.convex.com>
Sender: news@objy.com
Reply-To: peter@objy.com
Organization: Objectivity Inc.
Lines: 14

In article <thurlow.655915475@convex.convex.com>, thurlow@convex.com (Robert Thurlow) writes:

|> I agree that write(2) won't return you an error in general, but processes
|> can, at any point they wish, call fsync() to ensure the data is secured.
|> That ability is lost if the server is acknowledging only the receipt of
|> the request.

I am sorry.  I was being unclear.  I was only advocating writes become
asynchronous.  Calls like fsync (and close if we make it implicitly
fsync) would have to be synchronous.


	Peter Moore
	peter@objy.com