Go Back   cPanel Forums > cPanel® and WHM® (for Linux® and FreeBSD® Servers) > cPanel and WHM Discussions

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-26-2007, 05:30 AM
Registered User
 
Join Date: Sep 2006
Posts: 4
Lasers is on a distinguished road
Daily httpd restart changes AllowOverride None to All in httpd.conf

How do I disable the daily changes to httpd.conf? All occurrences of "AllowOverride None" are changed to "AllowOverride All" allowing use of .htaccess and increasing disk activity, which I don't want.

I've only noticed this occurring recently. I tried disabling all WHM updates to no avail. Tried making httpd.conf read-only by chmodding it to 0400, it automatically was made writable.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-26-2007, 09:20 AM
cpanelkenneth's Avatar
cPanel Quality Assurance
 
Join Date: Apr 2006
Posts: 3,222
cpanelkenneth is on a distinguished road
which version of cPanel?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-26-2007, 09:52 AM
Registered User
 
Join Date: Sep 2006
Posts: 4
Lasers is on a distinguished road
WHM 10.8.0 cPanel 10.9.0-C138
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-26-2007, 10:16 AM
cpanelkenneth's Avatar
cPanel Quality Assurance
 
Join Date: Apr 2006
Posts: 3,222
cpanelkenneth is on a distinguished road
When /scripts/upcp runs, it executes /scripts/checkallowoverride, unfortunately there is no (official) way to disable it. However you can do:

Code:
mv /scripts/checkallowoverride /scripts/.checkallowoverride
touch /scripts/checkallowoverride
chattr +x /scripts/checkallowoverride
Which will prevent it from happening. I'll see what can be done to make the application of checkallowoverride configurable. It's probably a legacy thing that someone requested long ago. It likely still serves a useful purpose for some, but should at least be configurable (meaning: run or don't run this script).
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-26-2007, 10:35 AM
Registered User
 
Join Date: Sep 2006
Posts: 4
Lasers is on a distinguished road
Thanks for being specific in your reply. However...

chattr +x /scripts/checkallowoverride

Returned "usage: chattr [-RV] [-+=AacDdijsSu] [-v version] files...". So, did a "chmod 0755 /scripts/checkallowoverride", which is the same value as /scripts/.checkallowoverride. I assume that has the same effect, making the file executable.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 02-26-2007, 10:49 AM
cpanelkenneth's Avatar
cPanel Quality Assurance
 
Join Date: Apr 2006
Posts: 3,222
cpanelkenneth is on a distinguished road
Yeah, it means I typed to fast and didn't double-check. Sorry, it's supposed to be:
Code:
chattr +i /scripts/checkallowoverride
The idea is to make it immutable (unchangeable).
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 02-26-2007, 11:15 AM
Registered User
 
Join Date: Sep 2006
Posts: 4
Lasers is on a distinguished road
It's alright. Thanks for the clarification. Good that I noticed the chmod difference.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 02-26-2007, 01:17 PM
cpanelkenneth's Avatar
cPanel Quality Assurance
 
Join Date: Apr 2006
Posts: 3,222
cpanelkenneth is on a distinguished road
The idea is to make the file unchangeable, since the next time /scripts/upcp runs, that file will be replaced since it no longer matches the integrity check. Hence the use of chattr +i to make it unchangeable.

A question for you, if you will. I checked /scripts/checkallowoverride and it's only supposed to change the AllowOverride directive when it finds the following:

Code:
<Directory />
AllowOverride None
# more directives
</Directory>
The key is the <Directory /> If the file path in the opening Directory statement is merely a slash (and only a slash), then the AllowOverride checks are performed (and possible changing your directive to All). If the AllowOverride statement is not in a Directory block, nor is merely a slash, the AllowOverride statement is skipped.

If the AllowOverride statement(s) in your httpd.conf do not match those two stipulations, and they are changed, would you mind posting those portions of httpd.conf here (or PM them to me) so I coudl examine them (feel free to appropriately sanitize them)? Thank you.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 12:09 PM.


Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
© cPanel Inc