example (note last line):
[tracker]
path = /usr/shares/tracker
read only = No
create mask = 0777
directory mask = 0777
force group = tracker
oplocks = no
After running testparm it looks like this share should also have:
level2 oplocks = no
This effectively fixes the problems for our application without having to disable anything on the desktop or affect oplocks on the other shares on the server (AFAIK).
Did you try disabling oplocks on the server and have it not work and thus have to disable them on the desktop?
Regards,
Cymen Vig
Jeff Davies wrote:
However, opportunistic locking corrupts ISAM and ISAM like databases.
Here is how to turn off opportunistic locking.
(NOTE: It has to be turned off at a system wide level, there is no provision in
windows to enable this for some file services and not for others.)
-----------------------------------------------------------
Opportunistic locking turned off on the Windows XP client in this way:
Start-Run->(type in) RegEdt32
navigate to \Hkey_Local_Machine\System\CurrentControlSet\Services\LanManServer\Parameters
new Key or type DWORD
name "EnableOplocks" leave value at default 0.
navigate to \Hkey_Local_Machine\System\CurrentControlSet\Services\LanManWorkstation\Parameters
new Key or type DWORD
name "EnableOplocks" leave value at default 0.
Close rededt32 and reboot.
- -------------------------------------------------------
This has solved our Goldmine database corruption problems (started when the
first Windows XP client was connected (all other machines were Windows 98).
Wizard Systems, makers of Goldmine has been notified, and the above information
will be on their support database.
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
