We are having a problem that I suspect is due to nmbd giving out obsolete information. Unfortunately the problem can not be reproduced consistently. 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? Tom Schulz Applied Dynamics Intl. schulz at adi.com
I have seen this too. But didn't mind for now because after adjusting DNS settings I haven't seen it again. Am 29. Januar 2015 18:12:08 MEZ, schrieb schulz at adi.com:>We are having a problem that I suspect is due to nmbd giving out >obsolete >information. Unfortunately the problem can not be reproduced >consistently. > >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? > >Tom Schulz >Applied Dynamics Intl. >schulz at adi.com >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba
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 Your problem sounds like a Windows caching problem: https://technet.microsoft.com/zh-tw/library/ff686200%28v=ws.10%29.aspx Regards, Marc