The Samba-Bugzilla – Bug 9284
problem setting ACL permission on shared folder: setting rwx but getting r-x
Last modified: 2012-12-04 12:02:17 UTC
Created attachment 8046 [details]
The attachement contains the level 10 log, and as well wireshark traffic
I am having problem setting permission on shared folder:
the folder is datasamba/common and after I set full permission (from win7) for a user itester (3000017) and also tester (3000018), I could see that it is only granting r-x to those users. but I could see from the default permissions that they have rwx.
[root@ramoffice ~]# getfacl /datasamba/common
getfacl: Removing leading '/' from absolute path names
# file: datasamba/common
# owner: root
# group: users
# flags: sst
[root@ramoffice ~]# wbinfo -i itester
[root@ramoffice ~]# wbinfo -i tester
Can any one also tell me how I can get info about the builtin groups, actually with wbinfo, I am only able to get:
[root@ramoffice ~]# wbinfo -g
Enterprise Read-Only Domain Controllers
Group Policy Creator Owners
Read-Only Domain Controllers
The log states this is version:
samba version 4.1.0pre1-GIT-615951e started.
which is a git-snapshot out of master.
While I appreciate the bug notification, we're trying to stabilize the 4.0.0 stream right now, and there have been significant changes between 4.0.0 ACL code and 4.1.0 ACL code.
Can you try and reproduce either out of the 4.0.0rc2 release, or at the very least with branch v4-0-test please ?
That way I have a known codebase to work with.
could you please guide me how I could get the 4.0.0rc2 release?
I see from the howto that I could get the samba_4_0_test as below, but from your post, I understand better I will take the 4.0.0rc2 release
rsync -avz samba.org::ftp/unpacked/samba_4_0_test/ samba-master
is it may be somewhere here:
You are the main man. I've tried it and it is working fine. thanks a lot.
will keep testing it, and will let you know If I find any issue.
(In reply to comment #3)
Can you please try to reproduce this one with 4.0.0rc6?
The reporter wrote that it's working fine now.
Closing out bug report.