I am learning SELinux from LinuxCBT and I'm stuck at one place. Now video is on RHEL 4 (so tell me if things has changed since, cause I can't find anything related) shows how to disable SELinux security on httpd. It's following way
Does anyone know which sebool it is to allow httpd write access to /home/user/html?
When I disable selinux echo 0 > /selinux/enforce I can write, so definitely selinux. Just don't know which one is the right one without opening a big hole and Google isn't being much help.
CentOs 6 64bit running apache 2.2.15-29.el6.centos.
When I try to stop/start or restart httpd I get an error that says it has failed. A tail of the error log is below. I also noticed that a httpd.pid file is not created even though it is configured in the main conf file.
If I set selinux to permissive, it works just fine. I do not want to run it with selinux disabled.
Hi all, i came across the following method of how to permanently disabling selinux and it's notifications. Although changing enforcement from the gui into permissive mode does most of the job, the notifications still pop-up when some applications are started.
So to disable it do the following:
I transfered some user from another server to mine...
I maked backup in cPanel and transfered it to my server, then I restored it via WHM.
Everything is ok.
But when I tried to restart httpd I get this
Warning: DocumentRoot [/home/monte24/public_html/montenegrobet.me] does not exist
Warning: DocumentRoot [/home/monte24/public_html/posao] does not exist
Warning: DocumentRoot [/ho
I have been using Fedora for about two years. I love it except one thing: I can not get used to SELinux. SELinux in Fedora evolves rapidly and it is not uncommon that an updated SELinux breaks up other things. So here is my question: is it really useful for a desktop which doesn't have a whole bunches of services running except OpenSSH? I am deciding whether to disable SELinux for good.