Sriram Natarajan wrote: > Seema > If I understand right, Apache HTTPd MPM's can be started in one of the > following ways > 1. /usr/apache2/bin/apachectl start (starts the default prefork MPM) > 2. /usr/apache2/bin/httpd -f /etc/apache2/httpd.conf (starts the > default prefork MPM) > 3. /usr/apache2/bin/httpd.worker -f /etc/apache2/httpd.conf (starts the > worker MPM) > 4. svcadm enable network/http/apache2 (currently starts only the prefork > MPM). > > If I understand right, what we want here is a common way to start the > apache server (both in prefork as well as in worker MPM) using apachectl and > SMF.
Correct. > Now, to do this, I was wondering, can we not implement in the > following way > - Add a new argument 'start-worker' to apachectl . So that, customers > can start the server in prefork or worker by using the common (well > known) apachectl script itself. > for example > apachectl start or apachectl start-prefork (starts the server in prefork > MPM) > apachectl start-worker (starts the server in worker MPM) The intention is not to change the apachectl interface which is exposed to the user. If Apache adds these options to the script, then we will end up changing the things at our end. > - Leverage the already existing /lib/svc/method/http-apache2 script > used by SMF to start the server in prefork or in woker depending upon > the SMF property. I was hoping , we can do this in the same way as this > script 'http-apache2' does for starting the server in SSL or non-SSL mode. Agreed. But, apachectl.smf script will essentially be a wrapper for the svcamd commands. -- Seema.
