Jyri Virkki wrote:
> I went through all the Apache threads so far this afternoon to
> summarize the current state of discussion, here is where I believe
> things stand:
> 
> - The next case will support both worker and prefork MPM. I believe
>   we have closure on this. Seema has posted details on the delivery.
> 
> - Configuration of MPM choice. Seema, can you summarize the answer?

Our Apache installation will have both prefork and wokrer mpm binaries. The 
default
server "httpd" will use prefork mpm model. The one that uses worker mpm model 
will be
named as httpd.worker. To choose between these servers, we can use one of the 
following

1. set HTTPD variable within /usr/apache2/bin/envvars.
        envvars is already sourced within apachectl. This is applicable when 
invoked
as SMF service as Apache smf service internally invokes apachectl.

2. use a smf property for the svc:/network/http:apache2 service.
        This works when Apache is started as a SMF service.

3. use a different (new) file "/etc/default/httpd" to define HTTPD variable and 
modify apachectl
to source this file.
        /etc/default is a deprecated method of storing configuration
information. Hence not recommended.


> - Closure on file layout versioning. The 2007/169 case had
>   /usr/apache2 (and corresponding places in /etc and /var). There's
>   been much discussion on whether to stay the course or permit minor
>   releases of 2.x to coexist (and there are several way to accomplish
>   that, but the higher order question is whether coexistence is the goal).
>   The main argument for this appears to be for upgrades, so that upgrading
>   from S10 doesn't break a working installation.

> - There was discussion of adding a 'build' directory. Closure?

Correction...we are not adding "build" directory. We are moving "build" 
directory
currently under /var/apache2 to /usr/apache2 directory.
Reason: apxs expects the build directory to be under "%PREFIX%" which is, in 
our case,
"/usr/apache2" dir.

There was also a discussion on including *.conf within httpd.conf-example file.
I think we have a closure on this. We will be retaining the existing commented 
lines
to include individual .conf files as well as adding a commented line to include
/etc/apache2/extra/*.conf files.

> - There were various proposals on directory name changes (modules,
>   conf.d) but the consensus was that names should not change unless
>   there is a strong reason. So I believe there is closure on existing
>   names (libexec, extras).
> 
> Thoughts? Corrections? Etc? Hit list reply...
> 
> 

Thanks and Regards,
Seema.

Reply via email to