SAMBA digest 1763

Stephen L Arnold arnold.steve at ensco.com
Thu Jul 30 04:22:08 GMT 1998


When the world was young, Klaus Kappel carved some runes like this:

> Date: Thu, 30 Jul 1998 12:05:08 +0200 (CEST)
> From: Klaus Kappel <kkappel at sha2000.de>
> To: samba at samba.anu.edu.au
> Subject: Locking with M$-Access 97
 
> This is a REAL problem on the way to world domination ;-)

> since we moved a MS-Access MDB (16 Meg) to samba, 
> it ist killing queries more than twice a day, loosing records, ...
> It seems the application has no chance to recognice locked records and
> inform the user. with smbstatus I get one locking entry for the first user
> accessing the database (like: DENY_NONE   RDWR), the second is not in the
> locking list. Is this behaviour normal?

[snip]

> Has anyone out there experience in debugging this locking case, testify
> the use of "fake oplocks", optimizing access databases running samba
> servers?

I'd go ahead and upgrade to the latest version (1.9.18p8 I think), 
as it has real oplock support.  Try it and report the results.  
1.9.18p9 will have even more stuff in it (that may or may not be of 
benefit to you) - see digest 1761.  Hope this helps.

Regards, Steve Arnold


****************************************************************
Stephen L. Arnold                               Systems Engineer
ENSCO Inc.                        email:  arnold.steve at ensco.com
P.O. Box 5488                         www:  http://www.ensco.com
Vandenberg AFB, CA  93437             voice: 805.734.8232 x68838
                                               fax: 805.734.4779
#include <std_disclaimer.h>       
****************************************************************


More information about the samba mailing list