I'm still not a big fan of removing the MPM settings from the httpd.conf file. All of the other extra .conf files contain supplemental configuration but the MPM configuration seems to be more along the lines of a ServerRoot or Listen. Despite the fact that these are technically module directives, MPM directives just feel more like core directives.
Brad >>> [EMAIL PROTECTED] Wednesday, April 06, 2005 8:42:37 AM >>> I'm pretty-much done shredding the default config and I will give a couple days for review before I merge it. Feel free to correct any problems you see. Things that I know are missing: - updates to docs: new-features, upgrading, apachectl (remove startssl), CHANGES - changes to windows config. The actual config file changes are easy enough, but I'm not sure my nmake/awk skills are good enough to fix the install. I think this config is far clearer and more manageable for a newcomer, and probably also for an experienced httpd-user. It is also more secure in that it has less features enabled by default. And it clears out a lot of cruft that had built up over the years. The disadvantages are that it takes a little more work to get some basic features enabled, and it may tempt some users into the "death by a thousand config files" syndrome, although it by no means forces them into this. You can see the new config here: http://svn.apache.org/repos/asf/httpd/httpd/branches/simple-conf/docs/conf/ Joshua.
