Hello,
I'm using emacs on a remote cifs-mounted filesystem (cifs is the next-generation samba filesystem client to mount windows-shares (my company chose for a Dell PowerVault 745N to store all our internal information)). All goes well until after some time emacs starts complaining that the file changed on disk, I guess meaning that the original file has a modified time stamp since emacs opened it.

I found out that the timestamps on the cifs-mounted filesystem contain extra information after the second by using a command like:

$ls --full-time -cifs-file.txt
$-rw-r--r--  1 gef users 0 2005-02-07 14:46:10.041579900 +0100 cifs-file.txt

while this is not the case for a local file (ReiserFS):

$ls --full-time local-file.txt
$-rw-r--r--  1 gef users 0 2005-02-07 14:48:11.000000000 +0100 local-file.txt

I somehow have the feeling that this could be causing the problem, for instance because emacs internally stores the initial file timestamp without taking care of the extra numbers, rendering into a different timestamp than the one with the extra numbers.

With this in mind, I have a few questions:

 ** Can I disable this timestamp checking behaviour of emacs?
 ** Any idea if these extra numbers are causing the problem?
 ** Any idea how I can solve this problem (I also mailed to Steve French, the cifs developer, for help)

Greetings,
Geert Fannes.

PS: I'm using Slackware 10.0 in combination with the 2.6.11-rc2 kernel and emacs 21.3.2 (the one the Slackware installs)