>
> >>>>> " " == Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:
>
> > When the writer closes the file, how do you make the readers
> > see the latest changes (assuming that you always open/close
> > files per transaction type).
>
> There is a convention amongst NFS clients that each client will always
> flush *all* changes to the server upon close(), and it will always
> check the file attributes upon a call to open() (and if the mtime or
> file size have changed, one flushes the page cache).
> This suffices to guarantee file cache consistency *provided* that only
> one client opens the file at any given time.
>
> If locking is used, all changes are flushed to the server upon
> taking/releasing a lock, and the page cache is guaranteed to get
> flushed upon taking a lock.
And remember- this depends entirely on the server working the way
lockd assumes. Some systems DON'T do this anyway, since locks are not
necessarily available except on the local system, and not on the server.
Even when they are available, race conditions will/can still void the
assumptions.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/