Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!voder!pyramid!ctnews!risky!pase70!scottl
From: scott@convergent.com (Scott Lurndal)
Newsgroups: comp.unix.wizards
Subject: Re: Need help with lockf(),open(..., O_SYNC), fsync() on SUN's
Message-ID: <3610@risky.Convergent.COM>
Date: 21 Mar 91 20:13:02 GMT
References: <1991Mar20.205800.14651@agate.berkeley.edu>
Sender: root@risky.Convergent.COM
Reply-To: scott@convergent.com (Scott Lurndal)
Organization: Unisys Network Computing Group
Lines: 19

In article <1991Mar20.205800.14651@agate.berkeley.edu>, bks@alfa.berkeley.edu (Brad Sherman)
writes:
|> [If this is the wrong group, I apologize and would appreciate a
|> pointer to the right one.]
|> 

  [ explanation of problem wrt sync over NFS ]

|> The locking/unlocking of file1 (and blocking caused by it) works fine.
|> Adding an O_SYNC (on sparc's) to the open() calls does not help.
|> No other processes are touching file1 or file2.
|> This is with the standard SUN distributed C compilers and libraries.
|> 
|> Are we doing something wrong here?
Yes, you are using NFS.   Data on the client is not guaranteed to be 
fresh.  (i.e. you may get stale data)
|> -------------------------------
|> 	Brad Sherman (bks@alfa.berkeley.edu)
scott