When I checked for the system-config-securitylevel on the instance of Fedora I have, it didn't exist (at least a whereis and locate couldn't find it). I initially did the chcon command, and was able to get the web pages working. Later I found the GUI method to turn this off (just happened to be physically at the server, not just an SSH session).
I agree with the earlier post on this though - it's probably best NOT to turn of selinux. But, in terms of getting something running the way we already know how, it's easier to not have to deal with selinux. I would only recommend this if one had control of the server, and knew what type of access is expected of the server. It'll be interesting to see what the future brings for selinux. I would think that if there is ever a security hole discovered with it, that it would be abandoned - why impose another layer that needs upgrades/maintenance, if it doesn't really prevent the problems it's supposed to protect against? My thoughts.... Shawn On Monday 28 February 2005 15:58, Jason Louie wrote: > This is due to SELinux... I was just working in the issue today. You > either have learn how to use chcon to set the permissions or disable > SELinux with the command system-config-securitylevel, (I choose the > latter.) SELinux will cause issues particularly with diffrent > partitions for each service, (at least for me anyways.) > > Just a note... if you choose to keep SELinux enabled expect similar > issues with postgresql, mysql and others. For me disabling SELinux > solved most the issues. _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
