Group permissions aren't working as expected in two different situations:
1. I have the following file:
-r--rw---- 1 apache_user developers_group 13285 Dec 9 12:53 index.html
I am a member of developers_group (not my primary group) and I can't edit this
file. If I give apache_user (the file's owner) the write permission then I can
edit the file. Why?
This only happens when I access the file through Samba, on the server itself
these rights work as I expect, i.e., no need of write permission to the owner.
2. I have the following directory:
dr-xrws--- 1 apache_user developers_group 0 Mar 18 2004 userimages/
Again I, as a member of developers_group, should be able to create a new file.
But I can't: permission denied.
I saw bug #1126 that seems the same as this except that, as per Paul Gienger,
bug #1126 is strictly Solaris related.
If Paul is right, I believe I'm actually reporting a new bug. If not, please
forgive me for the duplicate bug.
BTW I using ldap based authentication and I have "unix extensions = yes".
This same behaviour has been observed on a Samba 3.0.8 server.
Created attachment 839 [details]
Log leve 10 of file access resulting in readonly access
This is a log level 10 of a failed editing session of a file through Samba
which resulted in readonly access.
I expected read/write access.
Created attachment 840 [details]
Log level 10 of failed "touch new_file"
Log level 10 of a failed "touch new_file" through a Samba share.
I expected a successfull creation of the file.
Created attachment 841 [details]
My smb.conf file for your reference.
I think this is by design. The owner write bit is used to store the 'read only'
I believe you are right Andrew. It makes sense.
Even the Official HOWTO mentions it at
Thanks for your attention.
I think this bug can be closed if Andrew's info is confirmed.