James Kosin a écrit :
Jeremy Allison wrote:
- there is only one application (a CAO drawing tool) for which only
some files causes a violation error, even with kernel oplocks = No.
Looks like there was an interaction with the SAMBA-VSCAN module (version
0.3.6b) somewhere, as disabling this module removed the violation error.
Interesting. If that the latest version of vscan ?
Jeremy.
It is the latest, although 0.4.0 has been released as a snapshot. I
think maybe his problem is he may be using an older compiled version of
SAMBA-VSCAN that has not been compiled for the new version of SAMBA
installed.
I do know the source for vscan requires integration with the correct
version of samba; otherwise, unpredictable results happen.
Hello,
The SAMBA-VSCAN module I use has been compiled against the installed
SAMBA version. AFAIR SAMBA doesn't load a VFS module that has a
mismatched version.
--
Cédric Delfosse Linbox / Free&ALter Soft
152, rue de Grigy - Technopole Metz 57070 METZ
tél : 03 87 50 87 98 http://linbox.com
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
