[Samba] 'veto oplock files' option in 3.0.2a broken ???
tms3 at fsklaw.net
Wed May 19 17:10:52 GMT 2004
I suspect it has to do with the creation of the .lmd file, which is
created when someone opens an access database. It's probably being
created with the wrong permisions. There's a filter command for
smb.conf that stops things like this from happening.
Flávio Henrique wrote:
>I'm update my samba, from 2.2.8a to 3.0.2a, and now my 'veto oplock files' do no work...
>I set my option like this: veto oplock files = /*.mdb/*.MDB/
>but after the first user open our software (that opens a file .mdb in a samba share) the second user can't open... he gets the error message: 'Couln't lock the file'
>Even setting all locking options = no, the error persists...
>Someone already have the same problem ??
More information about the samba