On Thu, Feb 09, 2006 at 11:30:38AM -0500, linolil@equoria.net wrote:
>
> We are seeing a lot of inconsistant access behaviour on
> our server since upgrading from 2.2.8a to 3.0.20. The
> bottom line is that the Unix group permissions on the
> file system seem to be ignored.
>
> ================================================== ======
> [sharename]
> comment = shared files
> path = /export/directory
> force group = shared
> read only = No
> create mask = 0774
> directory mask = 0774
> guest ok = Yes
> hosts allow = 192.168.1., 192.168.2., 192.168.3.
> ================================================== ======
>
> Did the behavior of "force group" change from 2.2.8a to
> 3.0.20?
>
> When we set unix group restrictions on a folder or file,
> using a different group from the one listed in "force
> group", the unix access permissions do not work. People
> in the correct group do not get access. This used to
> work under 2.2.8a, but is now driving me crazy.


More information please. Give an example of what you expect
and what is happening using specific groups and files please.

Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba