Anybody understand SELinux?

Achim Gratz Stromeko at Nexgo.DE
Fri Dec 23 14:17:56 UTC 2016

Am 23.12.2016 um 04:59 schrieb Hal Murray:
> google tells me that's because SELinux is blocking access.

If you switch SELinux into permissive mode (from enforcing) the logs 
should tell you exactly which access would fail and for what reason. 
 From what you've been showing I think the config file needs to be in 
the system_u context in order for logrotate to not pick up any files 
that may have been dropped into the directory maliciously.


(on the road :-)

More information about the devel mailing list