3 Jan
2012
3 Jan
'12
2:41 a.m.
On 01/03/2012 03:30 AM, Bennett Haselton wrote:
In other words, when SELinux causes a problem, it can take hours or days to find out that SELinux is the cause -- and even then you're not done, because you have to figure out a workaround if you want to fix the problem while keeping SELinux turned on.
You can always set SELinux to permissible mode for testing purposes and it will allow the action, but report that it would have been blocked.
--
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant