nkelly at citrusnetworks.net
Thu Oct 10 15:28:01 GMT 2002
Can you see if you have oplocks enabled? Do a './testparm | grep oplock'
from your /bin directory. You will have to press enter to complete the
command. My output example is below.
If oplocks are enabled then you should turn them off I would say.
[root at belly bin]# ./testparm | grep oplock
kernel oplocks = No
oplock break wait time = 0
veto oplock files =
fake oplocks = No
oplocks = No
level2 oplocks = No
oplock contention limit = 2
From: Ramzi S. Abdallah [mailto:rsa at acl.edu.au]
Sent: 10 October 2002 03:13
To: samba at lists.samba.org
Subject: [Samba] Samba+MYOB
We are experiencing problems using MYOB Premier V6.0.2 on Windows 2000
computers SP3, with the data file residing on shared drive on Linux (Redhat
7.2) file server running Samba Version 2.2.1a and kernel 2.4.9-34.
The MYOB Tech support have told me that it is a problem with our network but
could not give me any hints where the problem might be.
The MYOB database has been corrupted at least 8 times over the last 4 days
and every time we have to go back to our backups thereby losing all of the
transactions entered in the interim.
Has anyone had any experience with a similar problem and could give me any
Following is the smb.conf configuration related to the MYOB share
comment = MYOB Directory
path = /data/MYOB
read only = No
admin users = @myob
Any Help would be highly appreciated.
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.394 / Virus Database: 224 - Release Date: 03/10/2002
More information about the samba