Apache status:
Open Issues:
-------------
- Supporting multiple versions of Apache
Should we use
/usr/apache2/2.2.4
or
/usr/apache2.4
-- If we are going to support multiple versions, then
* package name will change to reflect the latest version.
We will follow the php (2007/168) convention.
e.g., SUNWapch224d, SUNWapch224u
* Other dependents components' (mod_perl, svn, mod_auth_gss, php )
build files (e.g., Makefile.sfw) need to be modified to point to
the new location.
- Cohabitation of 32bit and 64 bit Apache installations
-- If we are going with both 32 and 64 bit installations, then
* Other dependents components' (mod_perl, svn, mod_auth_gss, php )
build files (e.g., Makefile.sfw)need to be modified to point to
the new 64 bit location.
- Supporting SMF way and/or non-smf way of starting Apache
This will decide where the property to choose multiple MPMs
should reside.
-- If it is only SMF, then we will use SMF property
else, we need to have it in a different file which will be
used in both smf and non-smf mode.
envvars cannot be used as it is under /usr .
- What do we do with /etc/apache2/extra and /etc/apache2/original
dirs and its contents ?
Apache creates /etc/apache2/original dir and populates it with
the new set of config files (httpd.conf and extra/*.conf). Then it will check
if the file with the same name already exists under /etc/apache2. If not,
it will copy the file under /etc/apache2.
Note: We need a closure on all the above issues asap. These are needed for the
ARC case.
Resolved Issues:
------------------
- Co-existence of prefork and worker mpms.
- Moving libexec dir from /usr/apache2 to /var/apache2
- Moving build dir from /var/apache2 to /usr/apache2
- Creating a new directory conf.d under /etc/apache2
- Having httpd.conf file under /etc/apache2 to support OOB apache startup
- Adding the following line to httpd.conf
Include /etc/apache2/conf.d/*.conf
Best Regards,
Seema.
