Quote:
|
Originally Posted by riganta
I used the command "chmod a+x file-name" to get around the
Riganta
|
All that will do is make the file executable by all users.
you should always check
/var/log/messages to see if there are any errors before playing with things...if there is nothing telling you what's going on in there...then try:
httpd.conf should need only be 644 permissions, or -rw-r--r-- (read by all, but writeable only by the owner, whcih should be root).
Do the following:
Code:
# cd /etc/httpd/conf
# ls -ltr
you should see:
Code:
-rw-r--r-- 1 root root 33677 Sep 11 httpd.conf
is this what is says?
if so, and you still can't write to it try this in the same directory:
Code:
# getfacl httpd.conf
you should see that the owner and group are set to root, and user::rw- group::r-- other::r--
if that is correct, and you still can't write to it do you have SELinux enabled? If so, check the security context of the file, shouldn't cause issues with writing it though.
if all this looks good, finally check
Code:
# cat /proc/mounts | grep root
this should return with a rw flag in the line