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: John W. Eaton
Subject: [Octave-bug-tracker] [bug #42242] Octave does not always execute most recently saved file in an NFS directory
Date: Fri, 1 May 2020 13:57:09 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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

Those results do appear to show some skew in the system time and the file
timestamps.  It seems to me that the mtime after editing the file should be
larger than the value of the system time from before editing.

Why the difference?  I'm guessing the clocks on the two systems are not
properly synchronized.  Are both systems running ntp?  Are the clocks tracking
the network time correctly?

Maybe we can avoid these kinds of problems by doing what I suggested in
comment #31.

But even if we make that change for Octave, I'd recommend ensuring that your
systems are all correctly synchronized to network time, or at least
synchronized among themselves.  NFS file systems work best when system clock
skew is minimized.


    _______________________________________________________

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]