David.Comay at sun.com wrote: >> 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 >> > > However, "extra" is the name currently used by the existing OpenSolaris > Apache. Unless there's a strong reason to change this (for example, > other OS vendors use something like "conf.d") I strongly suggest not > changing this. > > Other Apache re distributors does seem to converge on conf.d I was hoping that our implementation is not very different from other competitors. This way, customers don't have to read a lot of documentation if they want to migrate from Linux to OpenSolaris so as to take advantage of other cool features in Open Solaris. >> 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. >> > > /etc/default is a deprecated method of storing configuration > information like this. It seems that a smf(5) property for the > svc:/network/http:apache2 service is a better way of configuring this > information. > > Thanks for the suggestion. Very valid indeed. This also provides the flexibility for the server administrator to run apache httpd in different MPM model for any given zone.
thanks sriram
