From: Ladner, E. (Eric.Ladner) <Eri...@ch...> - 2003-08-04 15:36:33
|
Can you do a listing of the files outside of jedit and see the timestamp change periodically? If they do, I'd look for some kind of batch job or something that's scanning the files. Also, see if you can come up with some kind of pattern (i.e. it gets updated every 2 minutes or something), that may help the admin find what's touching it. Check also to see if the time on the file gets updated when you aren't even in Jedit. That would remove Jedit as a culprit. The only other thing to look at is to see if Jedit's autosave is bumping the time, but I doubt seriously it is since it saves to a whole other file. (Interesting.. Outlook's spell checker suggests "Jedi" as a replacement for "Jedit".. Jedit - the "May the force be with you" editor.) Eric -----Original Message----- From: Chris Petersen [mailto:li...@fo...]=20 Sent: Monday, August 04, 2003 10:09 AM To: Ladner, Eric (Eric.Ladner) Cc: Brad Mace; us...@je... Subject: RE: [ jEdit-users ] disabling auto-reload (4.2pre3)? > If there is a time difference between the client and the server, I=20 > could see where this could cause problems when saving a file. Say you > save a file and the server has a time that is a few minutes in the=20 > future. When the time on the file is updated, it's in the future=20 > compared to the client's time. I've had this kind of problem with=20 > makes across NFS before. This isn't the case with me, though. My machine and the files' servers should only be a few seconds different (we're all using the same time server), and I'm the only one using the files. Unless there's some way that the files' modification times are getting set by the server when nothing happens to them (which is exactly what it looks like is happening).... -Chris |