[Octave-bug-tracker] [bug #42242] Octave does not always execute most recently saved file in an NFS directory

[Michael Godfrey]

Follow-up Comment #8, bug #42242 (project octave):

Classifying the problem as as NFS issue will not
help to fix it. NFS behavior is fixed. The only
thing that can be done is to work around it. This
has been true for many years. 

Checking clock sync on the system that is failing
is the first thing to do. Next is to ensure that 
updates are correctly synced in the Octave code.
It may be necessary to introduce a wait while the
NFS write actually completes. NFS reports completion
before it is actually true (depending on the NFS
mount options -- these also need checking).

Many installations use async options on the mount command
for claimed efficiency reasons. This will guarantee
consistency problems. 

But, this is hardly the beginning of the NFS story...

Oh, yes, worth checking if this is happenning under
NFS3 or 4.  4 is quite different from 3.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42242>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/