Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Why RESTORE at all? Stop editing it!' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why RESTORE at all? Stop editing it!
Authored by: mithras on Feb 19, '03 04:35:00PM

Your advice is sound, but I don't think it applies to the loading/adding of Apache modules. Very often the loading is order dependent, so a directive placed in an later included file is not likely to work well.

Moreover, if you want to DISable a module that is loaded, I don't think you can do so, except by modifying the original httpd.conf (or using the apxs tool to do so).

---
--
<a href="http://mithras.homeunix.net/downloads">my free OS X applications and scripts</a>



[ Reply to This | # ]
Why RESTORE at all? Stop editing it!
Authored by: ScooterComputer on Feb 19, '03 11:39:30PM
I am currently loading and adding modules in my 1stoverrides.conf file (dav and ssl) with no problems. Yes, you can't UNLOAD a module, but by using ClearModuleList you might be able to rejigger your AddModule execution in an overrides file...try it and see. Plus, most current modules aren't as susceptible to ordering problems as old ones were.

My intention for recommending the 1stoverrides.conf file and not editing the httpd.conf comes from the fact that MOST of the complaints I have seen regarding OS X updates stomping on httpd.conf files are coming from ppl who aren't doing rocket science in the httpd.conf...and in their very general cases (where they probably aren't doing brain surgery with LoadModule/AddModule) then my Hint stands.

For those who ARE doing proper brain surgery in there, you a) know FOR A FACT (because you've tried it) that an Include override won't work, and b) don't go installing updates willy-nilly without backing up your configs and rechecking them after completing the update.

[ Reply to This | # ]