On Tue, Nov 02, 2004 at 10:27:35AM -0800, Jordan Michaels wrote:
Can anyone tell me what the default httpd.conf file looks like in SuSE 9.2?
Most likely it's similar to 9.1.
Can anyone give me a definitive answer on this?
I can. The configuration in 9.2 resembles the one of 9.1 very closely, plus minor fixes or adjustments. I understand your point but from feedback I know that most people are happy with the split because it makes life easier. It makes life _much_ easier especially when it comes to updates, have you ever merged httpd.conf{,.rpmnew} after a system update (or even security update) when httpd.conf is thousands of lines long? We are living in RPM land and you must be aware of the situation. BTW, a nearly identical configuration split into multiple files is currently happening upstreams (see recent discussions on httpd-dev). Thus, in some time all distributions might use the same multi file scheme (although some might stick to their own invention). Interestingly, the hight degree of similarity of what the apache developers came up with in comparison to SuSEs apache configuration shows how logically the configuration can be structured, i.e. the structure _does_ make a lot of sense. :-)
Perhaps, but not that I've seen. We do a lot of work with CentOS 3.1 because of it's compatibility with RHEL and it's httpd.conf is NOT broken up in to thousands (yes, I'm exaggerating) of includes. It's just one file, which, honestly, seems simpler to me then the hordes of includes.
Any problem with adding your one custom configuration file by simply dropping it into /etc/apache2/conf.d? Or include custom files via /etc/sysconfig/apache2? For building modules, use apxs2 -c, or apxs2-prefork -c to build a MPM specific module. Please tell me about _specific_ problems you are having. Complaining generically is not able to elicit improvements. :-) Peter