On 12/8/2010 3:41 PM, Warren Young wrote:
/That/ is my point. I could -- and sometimes do -- work around file permissions errors manually, quickly. SELinux has a higher order of complexity compared to Unix file permissions, so the associated fixes don't fit into a small, easy-to-mentally-model framework. Each fix therefore becomes a one-off that you have to write down in a document or script else you'd have to rediscover them with Google every time.
Is there any central reporting concept in SELinux so a multi-machine admin doesn't have to go check each for all of the one-off cases and knowledge can be shared about the fixes needed for 3rd party RPMs?