Samba 2.2, locking, databases

Jason Boerner JasonB at Computer.Org
Thu Nov 8 21:32:04 GMT 2001

I am responding to your post, listed below.  I am having the same problem with GoldMine which I believe
is written in much the same way as most clipper based applications.

Did you ever resolve the issue?  I just posted to the newsgroup but did not hear back yet.  I pormise to
post a summary should an answer show up.

I'm running 2.2.1a and will soon move to 2.2.2 to avoid oplock problem.

Thank You

*List:     samba <>
Subject:  Samba 2.2, locking, databases
From:     Tomas Potok <potok at> <>
Date:     2001-08-20 15:11:44 <>
[Download message RAW <>]*


I encountered a problem with $subj. I browsed through the archive of this list
and many others lists and I found many similar questions/problems but NO

The problem: I use an application written in Clipper (DOS) which uses database
and index files located on a samba share. When multiple users launch the app, a
strange error occurs, probably caused by bad file locking. The first one who
opens the database has no problems, but the other ones seem to be unable to open
the same database. The first client uses locking, but rarely on the whole
database, mainly only a few records are locked.

I tried many options in smb.conf, none helped. I don't want to fake oplocks as I
fear data corruption.

Anyone who can help? Any suggestions on how to test/verify this?



I have been infected, too.
Hi! I'm a .signature virus, copy me to your .signature to help me spread.
To unsubscribe from this list go to the following URL and read the

More information about the samba mailing list