Anthony Farrow:> Dear List,
>
> Samba Version : 1.9.18p4
> NT Version : SP4
> Visual Studio : 5.0 or 97
>
> Hi - I'm having a bit of a problem with visual studio and
> samba. I vaguely recall seeing something mentioned
> regarding this on this list before, so if I can take the
> liberty of picking your brains I would appreciate it.
>
> When working with a samba mapped drive, the user gets
> annoying messages along the lines of "The source file has
> changed, do you wish to reload the source file? (Yes/No)".
> At first I suspected a bug in visual studio, but after I
> gave the students access to a NT network drive the problems
> stop - so unfortunately the blame would appear to lie with
> SAMBA, which up until now has run flawlessly (keep up the
> good work!!!).
>
> I am aware Version 2 is out, but I can't consider this
> until I have tested it thoroughly in our test environment.
> This is not because I distrust Samba though, it's just a
> really busy period and slight glitch would be magnified
> into a large problem by moaning user types!!
>
> So, is there a fix for this? Has anybody any knowledge of
> this?
>
> I can post my smb.conf if necessary.
I have not any idea, but have you tried "dos filetime resolution" ?
|dos filetime resolution (S)
|
|
| Under the DOS and Windows FAT filesystem, the finest granularity on time
| resolution is two seconds. Setting this parameter for a share causes Samba
to
| round the reported time down to the nearest two second boundary when a
| query call that requires one second resolution is made to smbd.
|
|
| This option is mainly used as a compatibility option for Visual C++ when
used
| against Samba shares. If oplocks are enabled on a share, Visual C++ uses
two
| different time reading calls to check if a file has changed since it was
last read.
| One of these calls uses a one-second granularity, the other uses a two
second
| granularity. As the two second call rounds any odd second down, then if
the file
| has a timestamp of an odd number of seconds then the two timestamps will
not
| match and Visual C++ will keep reporting the file has changed. Setting
this
| option causes the two timestamps to match, and Visual C++ is happy.
/ Kari Hurtta