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: Jan
Subject: [Octave-bug-tracker] [bug #42242] Octave does not always execute most recently saved file in an NFS directory
Date: Mon, 05 May 2014 12:49:40 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0

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

Thanks for your comments, I did some tests:

- touching the file doesn't change the situation (ie. even if I touch the
file, octave does not execute the most recent version)

- NFS is mounted with sync, not async

- File timestamps:
 * Before editing:

  scalar structure containing the fields:

    dev =  23
    ino =  98435089
    mode =  33204
    modestr = -rw-rw-r--
    nlink =  1
    uid =  1001
    gid =  1001
    rdev = 0
    size =  2775
    atime =  1399293568
    mtime =  1399293567
    ctime =  1399293567
    blksize =  1048576
    blocks =  8

 * editing file

 * after editing:

  scalar structure containing the fields:

    dev =  23
    ino =  98435089
    mode =  33204
    modestr = -rw-rw-r--
    nlink =  1
    uid =  1001
    gid =  1001
    rdev = 0
    size =  2775
    atime =  1399293568
    mtime =  1399293577
    ctime =  1399293577
    blksize =  1048576
    blocks =  8

 * type displays the correct new file content, but octave executes the old
version

Please let me know if this is helpful and if I can provide additional
information.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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