I prefer httpd.conf too, but deleting the apache2.conf is no good idea. The only good thing about the apache2.conf is, that it includes the httpd.conf so all user defined configuration can be done in the httpd.conf and they can be seen very easily. But that is also possible if you include a completly new configuration file as myconfig.ext into the httpd.conf.
David On Mon, 2005-09-19 at 12:16 -0400, Angelo Bertolli wrote: > Jared Hall wrote: > > >PS I don't see why people who want more organization could have just > >done all this on their own without all that fancy reprogramming Debian > >did. Perhaps these changes to httpd configuration actually make httpd > >run more efficiently (less information being included at certain > >times)? code consolidation = efficiency. > > > > > I agree. Right now apache is compiled to use apache2.conf as the config > file, and then apache2.conf has a line to include httpd.conf. Why > couldn't httpd.conf have just had a line at the top to include apache2.conf? > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
