Hi ho there... Environment: IIS 6.0 with everything mapped to aspnet_isapi.dll and the webiste files on a Debian Sarge Samba 3.0.23a-1 server. Problem: When a file is changed on the Samba server, IIS keeps serving the old content as long as you keep requesting the file. What I know so far: Because everything is mapped to aspnet_isapi.dll, everything is cached in the kernel-mode-cache on the Windows machine. When changing the change notify timeout to 5 seconds it takes 5 seconds for the content to change... BUT!!! But when I don't wait 5 seconds en keep refreshing/requesting the page every 2 seconds, the content never changes?!?! Only when I stop refreshing for at least the time set as the change notify timeout, the content will be updated... Any advice on this? If not I'm affraid I'll have to set the change notify timeout to 1 second which is quit costly for my system (if I understand correctly that is)... Regards, Sander
Gentlemen, Developers, Please take a look at my post below. Especially the part that starts with "What I know so far" and "BUT!!!"... Could this be a bug in Samba? Please respond... On ma, 2006-08-14 at 13:04 +0200, S. J. van Harmelen wrote:> Hi ho there... > > Environment: IIS 6.0 with everything mapped to aspnet_isapi.dll and the > webiste files on a Debian Sarge Samba 3.0.23a-1 server. > > Problem: When a file is changed on the Samba server, IIS keeps serving > the old content as long as you keep requesting the file. > > What I know so far: Because everything is mapped to aspnet_isapi.dll, > everything is cached in the kernel-mode-cache on the Windows machine. > When changing the change notify timeout to 5 seconds it takes 5 seconds > for the content to change... > > BUT!!! But when I don't wait 5 seconds en keep refreshing/requesting the > page every 2 seconds, the content never changes?!?! Only when I stop > refreshing for at least the time set as the change notify timeout, the > content will be updated... > > Any advice on this? If not I'm affraid I'll have to set the change > notify timeout to 1 second which is quit costly for my system (if I > understand correctly that is)... > > Regards, > > Sander >
On Tue, Aug 15, 2006 at 09:28:38AM +0200, S. J. van Harmelen wrote:> Please take a look at my post below. Especially the part that starts > with "What I know so far" and "BUT!!!"... Could this be a bug in Samba?Yes, it is a known bug in Samba that is not easy to fix. Tridge has figured out how the notify stuff should really work only a couple of months ago. It is on our list of things to implement in Samba3. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20060815/7251c39d/attachment.bin
Thank you very much! That was what I needed to know... Now I can stop searching and wait for the update to come out... Any idea when this should be implemented? A few weeks? A few months? Thanks again! On di, 2006-08-15 at 09:42 +0200, Volker Lendecke wrote:> On Tue, Aug 15, 2006 at 09:28:38AM +0200, S. J. van Harmelen wrote: > > Please take a look at my post below. Especially the part that starts > > with "What I know so far" and "BUT!!!"... Could this be a bug in Samba? > > Yes, it is a known bug in Samba that is not easy to fix. > Tridge has figured out how the notify stuff should really > work only a couple of months ago. It is on our list of > things to implement in Samba3. > > Volker