octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #42242] Octave does not always execute most re


From: Michael Godfrey
Subject: [Octave-bug-tracker] [bug #42242] Octave does not always execute most recently saved file in an NFS directory
Date: Fri, 1 May 2020 19:56:27 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

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

I have made extensive use of NFS. It has always had
problems with synchronisation. And, of course, if
participating systems do not have synchronized clocks
problems will occur that are not entirely the fault of
NFS. Various defensive measured have been used including
file close and read back after all writes. 

Certainly, being sure to flush any buffers is necessary
in any case. And, all machines should be running ntp.
And NFS sync should always be used.

My experience suggests that including a file close and
reopen on NFS files may help but is not always reliable.

For full reliability I always ran everything locally with
a lock set and then transferred the results to the nfs
system.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]