> I was hoping we will use 'conf.d' as a wrapper directory for all task > specific configurations underneath and totally not need a directory like > 'extra'. I thought, the name 'extra' sounds yucky
If you see our directory structure, /etc/apache2 contains only configuration specific files. Rest are under /usr/apache2 and /var/apache2. So, "extra" under /etc/apache2 would imply that this dir would contain additional configuration files. >> Similarly, can't we use the existing file, "/usr/apache2/bin/envvars" >> (already sourced from apachectl), for setting the variable >> "HTTPD" which determines the server mpm that would be used at startup ? >> > I was hoping , envvars will also source its variables from > /etc/default/httpd. Customer should have a easy way to switch between > multiple MPM. IMO, /usr/apache2/bin/envvars is not a very intuitive > place that one would look for to switch between multiple MPM. Besides, > /etc/default holds all system wide default configurations. > Any better suggestions are always most welcome As I mentioned earlier, sfw installs all apache specific files are under <either /etc or /usr or /var>/apache2 (apache2 is common). So one would expect apache2 related files to reside under one of these directories. The same convention can be followed for this file too. The purpose of "envvars" is to provide an option to the user to manipulate some settings of apache2 at startup. If the location is the issue, since it is more like a config file, it can be moved under /etc/apache2. I'm OK to add the additional file under /etc/default, but I think is unnecessary. Regards, Seema.
