Seema Alevoor wrote:
>
> 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.
By this do you mean having to edit the contents of /usr/apache2/bin/envvars?
Since /usr can be read-only, that won't work. If it's a config file
that may need editing, it'd need to end up somewhere under /etc
> 2. use a smf property for the svc:/network/http:apache2 service.
> This works when Apache is started as a SMF service.
In the context of this Apache that is part of Open Solaris, is there
an intent to support other ways of starting it?
As part of answering this it'll be useful to look at what is there
now. In S10 are the multiple supported ways of starting it?
My feeling here is that it is a daemon and this is [Open]Solaris, so
the supported way is smf. But if I'm missing some historical context
let me know.
> 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.
I'm not that familiar with the history of this location but if it is
deprecated then so it is, we shouldn't use it.
> 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.
So is it the case the apxs is broken right now in S10 when it needs to
find the build dir?
IIRC you mentioned sometime before that the contents of this build
directory are static (only delivered by the OS install/upgrade, cannot
change otherwise). If so, then /usr/apache2/build/ makes sense to me.
But if there is some scenario where administrators might need to
change the contents of build then /usr isn't right.
Do you know why it ended up in /var/apache2/build originally? Was that
just a mistake?
> 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.
Is it an issue if someone uncomments everything, thus including every
.conf file twice? That could be solved by comments in the file ("don't
do that"), but just curious.
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
