[Samba] Re: myob
John H Terpstra
jht at samba.org
Wed Dec 24 07:38:59 GMT 2003
Have you read the chapter in file and record locking in the
You need to disable oplock support on the share.
oplocks = False
level2 oplocks = False
Chapter 14 of the HOWTO also documents Windows registry settings you may
have to set in order to protect the MYOB files.
Above all, make certain that your hardware is not defective. Too many file
corruption problems are due to bad networking cards, and bad HUBs.
Also, absolutely do NOT use force user and force group - they will cause
you problems. Follow the chapter on File, Directory and Share Access
The solution is to decide what group and user you want to own the files.
Then on the directory do:
chown -R user_name.group_name directory_name
chmod ug+s directory_name
This sets the super-user bit on the directory so all files created will be
owned by that user and group. This has much lower impact than doing force
PS: force user = 'user_name', not Yes/No! Same for force group.
I hope this helps.
On Wed, 24 Dec 2003, Newtrend I.T. Specialists wrote:
> HI THERE
> thankyou for taking the time to help me i do rreally apreciate it
> the code i am using looks like this
> path = /etc/myob
> writable = yes
> guest = ok
> public = yes
> force user = yes
> force group = yes
> the shar is there and is ok but the problem is in with myob the file keeps
> on corrupting after a while with multiple users plugged in , i am told that
> this is because of myobs lock file system where a lock file is created for
> evey user that logs on, but samba doesnt like it is there any special
> commands i can use to give every one total and full access all at the same
> kind regards nic
John H Terpstra
Email: jht at samba.org
More information about the samba