David.Comay at sun.com wrote: >> The initial proposal mentioned about a new directory, "conf.d" under >> /etc/apache2 to host various Apache 2.2.4 >> server configuration files. I don't think we need this new directory. >> We already have "extra" directory under >> /etc/apache2 which can serve this purpose. Currently, >> httpd.conf-example file explicitly includes >> (but the lines are commented) all the .conf files under >> /etc/apache2/extra dir. > > Sorry, which proposal mentioned the "conf.d" directory?
http://www.opensolaris.org/jive/thread.jspa?threadID=36272 has the proposal. >> Instead, we can include the following line (commented by default) in >> httpd.conf-example file. >> Include /etc/apache2/extra/*.conf > > Actually, I think the current scheme of listing the Includes > individually is nicer as it's clear you can choose which extras to > include or not. Adding this line lets the user to just put the required conf file under this directory without the need to update the httpd.conf file. By default, this line would be commented. If adding this line and retaining the existing scheme provides greater flexibility, then we can even do so. >> 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 ? > > Why isn't a smf(5) property for svc:/network/http:apache2 being used to > control this configuration? Correct me if I am wrong. This property is used when the server gets started as a SMF service which internally invokes apachectl. This script uses HTTPD var to start the server. But for a user who doesn't want to run it in SMF mode, wouldn't it be better to provide the settings within envvars file ? Thanks and Regards, Seema.
