On 16 Dec 2002, Timo Sirainen wrote: > Are there some known problems related to ctime changing by itself? I > didn't find anything with google at least. tar seems to be complaining > about it all the time: > > [cras@hurina] ~% tar cf test.tar /mnt/cygwin/home > tar: Removing leading `/' from member names > tar: /mnt/cygwin/home/Timo Sirainen/xxx/xxxxx.xxx: file changed as we read it
Yes, this is known. smbfs does some strange time operations when closing a file. I think the idea is to make sure the time is changed when a file has been written to (NT4 doesn't, or not always?). I had someone that I thought I had tricked into testing this but I haven't heard anything for a while. The relevant code is (probably) this file/function in the kernel source tree: fs/smbfs/proc.c:smb_proc_close_inode() Try removing the "Kludge alert" parts and if that fails, the smb_proc_setattr_ext() call. Or wait until I get around to it. /Urban -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
