Leendert Meyer wrote:
I could send you a tarball of 9.2's /etc/apache2, right after installation (i.e. pristine) if you like.
That would be great. =) Thank you.
In SuSE 9.1, the default httpd.conf file was simply a bunch of includes. The docs said it was to help make things simpler, however, the reverse happened. I found that this setup made SuSE 9.1 incompatible with a lot of third-party programs that installed and worked just great using the standard httpd.conf file (without the includes). I was able to get my own program to work once I figured out where everything I needed was and adjusted the config settings accordingly, but it would have been MUCH easier if the httpd.conf file was normal.
Hmm.. I think that file IS "normal" esp. for Apache 2.0x. that came with popular distros. (Could be different if you compile it yourself...)
Perhaps, you're referring to the one that came with Apache 1.3x.
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.
That is just a point of view. If one installs a package that involves a configuration change in Apache2, what would be more simple that just drop a file in the right place? (needs a 'SuSEconfig --module apache2 && rcapache2 restart' afterwards)
Agreed, the simplicity part is a point of view. However, our problems come when trying to install thrid-party programs. Most of the third-party programs expect everything they need to modify to be readily available in the httpd.conf file itself, not in some include. This makes configuration a pain in the next for these thrid party programs. That's all I'm saying.
For those of you who have a copy of 9.2, I'd appreciate your insight. This will greatly effect our purchase decision with SuSE 9.2.
You can change the httpd.conf file to suit your taste.
I know, and I did. It would just save us many, many hours if we didn't have to talor it for every server that we set up. Time is money and SuSE is starting to take more of it! *NOT* cool! I'm a big fan of SuSE and have been for a long time - but this bothers me. It'd be nice to have the option of the default install being just one file.
Maybe you can leave SuSE's httpd.conf for what it is, and use your own: put the location in /etc/sysconfig/apache2, variable 'APACHE_HTTPD_CONF' on line 29.
Cheers,
Leen
Yeah, depending on the other benefits of 9.2, that's probably what we'll end up doing. We'll simply replace the httpd.conf file that came default with our own, pre-made one. A pain in the neck, but it works. Thanks, JM -- Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ jordan@viviotech.net