Schaefer Jr, Thomas R. wrote:
I don't know if it's by design or not.I've been messing with it some more. Yeah, you can take ACL's out of the picture. It basically boils down to in UNIX, even if the owner of the file does not have write access, if the group does have write access and you are a member of the group you can write to the file.
With Samba, at least by default, you can't. Its like Peter is saying, Samba seems to mark the file as read only since the owner doesn't have write access and that is that. It doesn't matter if the file actually is writeable by me due to my group membership.
Now I don't know if this is by design, and/or exactly how it can be
finessed into behaving differently via some of those other directives
such as "store dos attributes" and what not. But what I can say is that
to me nothing seems to have changed as far as all this goes between
3.0.11 and 3.0.14a. I've done some testing of this matter today on both
versions.
Looks to me that the read only flag in windows is triggered by the write bit on the primary owner.
IMHO use "delete readonly = yes" to get the unix semantics.
Refer my previous post on this
http://lists.samba.org/archive/samba/2005-April/103959.html
Regards, Doug
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
