[Samba] nmbd keeping old data

[Thomas Schulz]

> Hello Thomas,
> 
> Am 29.01.2015 um 18:12 schrieb Thomas Schulz:
> > We have a build system that runs on our Solaris machines where the final
> > files are copied into a distribution directory after being built. Note
> > that copying a new file on top of an old one does not change the file ID.
> > 
> > PC users sometimes will see the file as having the date as it was before
> > the updated file was copied into place.
> > For users running Windows XP, they do get the new contents. For users
> > running Windows 7, they may well get the old contents as Windows 7
> > will cache recently accessed files and not re-transfer them if the date
> > has not changed.
> > 
> > I have tried touching the containing directory and touching the file to
> > update the dates again, but the PCs contunue to see the old dates. If
> > I delete the file and then copy it back in again then the PCs finally
> > see the new file correctly.
> > 
> > Am I correct in thinking that nmbd is sometimes caching old information
> > and refusing to update it's view of things? Are there any settings that
> > affect how nmbd may cache data?
> 
> I'm not sure, why nmbd should have anything to do with this?! It does
> name resolution. https://www.samba.org/samba/docs/man/manpages/nmbd.8.html

I was assuming that nmbd was involved in listing the contents of
directories/folders. I should have read the manual pages before posting.
> 
> Your problem sounds like a Windows caching problem:
> https://technet.microsoft.com/zh-tw/library/ff686200%28v=ws.10%29.aspx

It can not be caching in the PC. I went to a PC that had not viewed that
share before and it also showed the date of the previous version of that
file. Other people have rebooted their PCs in an attempt to see the correct
date and still saw the old date. And, as mentioned above, the incorrect date
still shows up after touching both the file and the containing directory.
Now after rebooting they would get the new contents if they opened the file.
And people who have made the registry change as showen in that Microsoft
article will usually get the correct new contents. The incorrect date will
eventually clear, but it may take 4 or 5 hours for that to happen.
> 
> Regards,
> Marc

Tom Schulz
Applied Dynamics Intl.
schulz at adi.com