On 8/31/10 12:30 PM, AJ ONeal wrote: > Most files will be generated new and it would be nice to have the ACL > inheritance for those cases. > > I know can also make the shared group the default group, etc, but as > time goes on I think ACLs may be the best option. > > AJ ONeal
It's been a while since I did any ACLs, but I can try, I guess. FYI, a good example of needing ACLs would be a situation in which you want different permissions for different groups of people. For example in the College of Engineering system (CAEDM), they at least used to allow user-created groups, and automatically have a "read-only" group associated with it. The "read-only" group is a separate GID, and access is based on ACLs. I don't know how to do this beyond using ACLs. Anyway, no guarantees of the syntax here. I'm just trying to grasp at some very-old memories, plus looking at the setfacl man page. #Add rw for user john setfacl --recursive -m u:john:rw /home/shared #Add rw for user james setfacl --recursive -m u:james:rw /home/shared #Add default rw for user john setfacl --recursive -m d:u:john:rw /home/shared #Add default rw for user james setfacl --recursive -m d:u:james:rw /home/shared Is that roughly what you were after? -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
