disable caching in NFS
Subsystems (2)
The application (vi) is opening the file, and
the Linux NFS client should be implementing
close-to-open semantics (meaning that the client will revalidate its cache against the server upon every open). Thus, this should not be necessary. Of course, if the server does not update the file's modification time upon every write, or if it does, but uses coarse granularity (e.g. one second), then close-to-open semantics won't work. In that
event, the strategies Chuck Lever mentioned are among
what you can use to force the cache to be flushed or unused.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs