Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If I create a new filesystem/directory off of / and I set the Linux permissions to 770 I expect the group to be able to read and write files in that directory. SELinux was preventing me from doing this until I changed the SELinux type on that directory to public_content_rw_t. If this is just a directory in which users in that group will share files is this an acceptable SELinux type or should I be using another one? Writing a custom policy seems like overkill for these purposes.


share|improve this question
It will depend on what you plan to do in that directory. But in most cases, yes public_content_rw_t is fine. – Matthew Ife Nov 6 '11 at 22:51
Share files with what program? public_content_rw_t might be too much since it's for all programs, while for example samba_share_t is just for samba. – Cristian Ciupitu Nov 7 '12 at 23:12
ls -lZ dirname


ls -l 

but look at the 10th location on the directory line. If there is a "+" after the 3 rwx triplets, then there is an acl associated with the directory at the minimum. A chmod will remove the acl though. See also getfacl,setfacl, etc.

share|improve this answer
chmod won't always remove all ACLs associated with a file - If the + persists after a chmod you must use setfacl to clear the ACL entries. – voretaq7 Nov 17 '12 at 3:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.