Hi,
I had the same issue. In may case the `force group` option had the
problem. If I removed it, there was no `read-only` problems.
I saw that your other shares have the same option, so it is a bit
strange...
You can also try to upgrade to version 3.2, as this `force group`
problem is solved
Hi...
I wanna use samba 3.0.28 (on FreeBSD 7.0) machine just to serve some
shares with different content.
We have several users, and access to a share should be managed by the
unix group a user is in. so if the user is a member of the group
'business' he has access to a share called business.
