On Wed, May 21, 2003 at 05:29:58PM -0400, Steve Losen wrote:
My guess is that the application is doing more than a simple file open. Perhaps it is an editor that is creating a .bak file or something like that.
I know of at least one editor that runs on Windows that does something like that - it creates a temporary file, does its writes to the temporary file, and then, if you save your work, it renames the temporary file to the regular file name, presumably so that you don't lose your work if a write to the temporary file fails.
The executable image for that editor has the name "WINWORD.EXE". People have been known to run that on Windows every once in a while. :-)
Given that, I'd expect running Word on a document to change the mod time on the directory containing the file even on NTFS - and, in fact, it did that when I tried it on a directory I created in C:\TEMP.
I can think of one other possibility, but I have doubts since this is a NTFS volume. If you create a directory with NFS, then it is not in unicode format (unless you specify an option to change this). The first time you access the directory via CIFS, it is converted to unicode, and this might also trip the directory mod time, but I don't know.
No, it just changes the inode change time; that's sufficient to cause it to be dumped by "dump".