Silly me. The default oplocks=yes in Samba-1.9.18p* got me, that is,
the client aggressively caching files. Setting oplocks=no for
that particular share solved the problem.
Peter Debus
>
>
> re: Samba-1.9.18p8
> Windows 95 client connected to a read-write Samba file share .
>
> If a file is modified from Unix, Windows 95 client does not see the changes
> made when the file is opened read-only, the file prior to the modification
> is read. If the windows 95 client opens the file with read-write (opened
> in an editor) the current modified file is read.
>
> Any suggestions?
>
>
> Peter Debus
> School of Mathematical Computer Sciences
> University of New England
> Armidale NSW
> Australia
>
> Ph: 61 (0)267 73 2412 Fax: 61 (0)267 73 3312
>