-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Lueck wrote: | Gerald (Jerry) Carter wrote: | |> File Access checks is done by the OS. There is no |> associated tdb for file system perms. | | Say Jerry, I didn't catch where you were going with that. I am | suspecting share level access issues, not file level. Currently | I have not gotten into ACL's and all of that fun. | "write list = @mygroupname" etc... is how they should be | able to write.
ok. I know you have gotten this resiolved by starting with a clean server, but this is for the archives.... There are several layers of access control. You always get the most restrictive set. Think of them as filters that you have to successfully pass through (similar to PAM). There are two places of share access control. The first is the share ACL stored in share_info.tdb (for now) and defaults to Everyone (Full Control). The second layer is the read/write list, read only, et.al. in smb.conf. Then once you get to the file system, the OS says yes or now based on the on-disk permissions and your current uid/gids list. Hope this helps. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDdMVUIR7qMdg1EfYRAm3+AKDTRdO8ffdllNMf6+UIoVWD6imO7gCg1M8I QZDo0JMbSTCfVXJtxCrQHjo= =sVFy -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
