If I use parameter force group="some_group" in smb.conf, primary group of connected user (specified in /etc/passwd) is no more used for file access checks. This is different behaviour from previous versions of Samba (including 3.0.10) which makes some configurations unusable. Tested on FreeBSD 4.11 & Samba 3.0.11. If Samba is reverted to 3.0.10 on the same system, it works right.
(In reply to comment #0) Same for me: Linux 2.4.27-ct-1 (Debian) and Samba 3.0.14a-Debian ; makes my configuration unusable, possible workaround makes me headaches.
The manpage for 'force group' says: This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. So this behaviour is by design. Diff'ed 3.0.10 and 3.0.11, and I did not find any reason why the behaviour changed. What was the behaviour you have seen in 3.0.10? Volker
> What was the behaviour you have seen in 3.0.10? Look on this example: (part of) /etc/passwd: joe:*:1004:1004::/home/joe:/bin/sh (part of) /etc/group: groupa:*:500: joe:*:1004: (part of) ls -ld /data/testfolder drwxrwx--- 19 root joe 512 May 18 2004 /data/testfolder If I have share with path=/data and I set force group=groupa I cannot access testfolder logged in as user joe. Before the change it was possible because group "joe" is primary group of user "joe" specified in /etc/passwd and this group membership was not lost even when the primary group was set with "force group" to something diferrent (probably samba moved previous primary group to additional group list of the process, but it's only my opinion).
Can you send me a debug level 10 log of your 3.0.10 installation's smbd doing this? I can't reproduce it here. Volker
This bug looks like the same to the one in https://bugzilla.samba.org/show_bug.cgi?id=3990 Please, try latest 3.0.25a version of Samba to see if this problem is fixed. With best regards, Timur
*** This bug has been marked as a duplicate of 3990 ***