2009/12/16 Anton Starikov <ant.stari...@gmail.com>: > > On Dec 16, 2009, at 9:45 PM, James Peach wrote: > >> 2009/12/16 Anton Starikov <ant.stari...@gmail.com>: >>> One question. >>> >>> The fact that client ignore ACL capabilities of server, it is also normal >>> for current smbfs implementation? >> >> Even in 10.5, the smbfs client does not ignore the filesystem ACL >> support attribute. > > With unix extensions enabled? > > Then I don't understand. Where is the problem. > > On server side I see > > smbd_audit: antst|xxx|antst|sys_acl_get_file|ok|. > smbd_audit: antst|xxx|antst|sys_acl_get_file|ok|. > smbd_audit: antst|xxx|antst|sys_acl_get_entry|ok| > smbd_audit: antst|xxx|antst|sys_acl_free_acl|ok| > smbd_audit: antst|xxx|antst|sys_acl_free_acl|ok| > smbd_audit: antst|xxx|antst|get_nt_acl|ok|. > > > a file: > > # getfacl /home/antst/tt1 > getfacl: Removing leading '/' from absolute path names > # file: home/antst/tt1 > # owner: antst > # group: cmsusers > user::rw- > user:mohand:rwx > group::r-- > mask::rwx > other::--- > > And on client side: > > ls -le /tmp/qq1/tt1 > -rw-r----- 1 antst cmsusers 0 Dec 16 20:19 /tmp/qq1/tt1 > > > And if I try to set ACL from OSX I get > $ chmod +a "mohand allow write" /tmp/qq1/tt1 > chmod: Failed to set ACL on file '/tmp/qq1/tt1': Operation not supported > > Looking into the source code of client (thanks for link) I see that > CIFS_UNIX_POSIX_ACLS_CAP is not referenced in the sources (except header > file, where it is defined). Although it can mean nothing and you can use > somewhere in the code just numerical value.
It doesn't use unix ACLs, it uses SMB ACLs. -- James Peach | jor...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
