Craig White wrote:

>call me a non-believer but - did you 'refresh'?
>
>I'm just wondering if there is a 'redirect' of a share going on -
>meaning an SMB mount on a Linux box which is then sharing it via Samba
>to other Windows users - then there might be a significant lag time of
>when the Samba share actually gets updated file information.
>
>Consider using some patience and checking back (and a refresh) every 5
>minutes and my guess is that the change will eventually percolate down
>to the filesystem.
>
>Craig
>
Your suggestions are interesting but I don't think it explains what I am 
seeing.  Perhaps if I give you more detail, you can see why.

I have two computers on my desk.  One is Win2k with some code in a 
shared directory.  One is the Red Hat Linux 7.3 with my preferred 
editor.  I smbmount the Win2k shared directory to the Linux box and edit 
the code there "in the mount point" so to speak.  I save the code in the 
editor.  I then run the compiler on the Win2k box via GNU Make.  Make 
uses the date and time stamps to determine which source files need to be 
compiled because they are newer than the object files.

I have made an edit and saved it from the Linux box and then brought the 
same file up in an editor on the Win2k box and seen the changes.  But 
the date of the file was not changed.  I have then unmounted the share 
from the Linux box which should flush any "left over" file system stuff 
without having to wait 5 minutes.  The date did not change.

BTW, the filesystem on the Win2k is FAT32, not NTFS.

I have googled around and found a "dos filetimes" setting for the samba 
server that will allow non-owners of a file to change it's date and time 
but I don't think that applies here.  The SMB server is the Win2k box 
and I could not find a samba config file for the client smbmount side of 
things.

The answer is there somewhere, I just have not found it yet.  It's got 
to be a setting that I don't know about which is a lot of them since I 
am not a samba "expert" at all!

Alan