On Thu, Jun 22, 2006 at 04:09:31PM +0200, Cedric Delfosse wrote: > > I'm answering to myself. My problems are fixed: > - kernel oplocks = No has fixed the violation error for some > applications. Why the oplocks are refused is unknown, but for now I > don't need them ;
Yes, that would definately fix any kernel oplock problems (turning them off). > - 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. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
