Strange problem with emacs

lentzjm · 12-09-2008, 02:32 PM

I have a user here, that uses emacs 21.3-4.1 on RHEL WS 3. The user opens a file, edits it for a bit and goes to save, but when he tries to save, it says the file has changed. No one else has access to the users directory, and the file content does not change, but the timestamp does. The timestamp is newer than the original time so it complains. Has anyone experienced this? The files are located on an NFSv3 share on a SAN. There is nothing in NFS that would cause this AFAIK. And the SAN is showing no problems.

TB0ne · 12-09-2008, 02:56 PM

Quote:

Originally Posted by lentzjm

I have a user here, that uses emacs 21.3-4.1 on RHEL WS 3. The user opens a file, edits it for a bit and goes to save, but when he tries to save, it says the file has changed. No one else has access to the users directory, and the file content does not change, but the timestamp does. The timestamp is newer than the original time so it complains. Has anyone experienced this? The files are located on an NFSv3 share on a SAN. There is nothing in NFS that would cause this AFAIK. And the SAN is showing no problems.

It's because the NFS share is changing, somehow. I've seen this on NFS shares before, and if you move the file to a local device, it'll work fine.

I've never pursued this much, since the fix (for me) was just to edit local files, and move them back to NFS when I was done....

lentzjm · 12-10-2008, 09:39 AM

The other thing I'm curious about is this user is running tq.el and clearcase.el plugins for emacs. Maybe one of these are causing the problem?

TB0ne · 12-10-2008, 10:50 AM

Quote:

Originally Posted by lentzjm

The other thing I'm curious about is this user is running tq.el and clearcase.el plugins for emacs. Maybe one of these are causing the problem?

Probably not....as I said, I've seen this exact problem before, and it has to do with NFS. I've seen it in VI, emacs, Anjuta, and KDevelop, and the only common piece was the source file, being on an NFS share.