Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of tevans.uk@googlemail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <b55b8b45-2018-44b8-8830-875d615651f1@zimbra1>
References: <0E3C5199-5565-4D1E-8FCA-871A4338FC78@jaguNET.com>
	<b55b8b45-2018-44b8-8830-875d615651f1@zimbra1>
Date: Wed, 7 Mar 2012 10:18:40 +0000
Message-ID: 
 <CAFHbX1+Cqdjh0sdgcqGWEpuGoHk7Dcnt6aKtfHG-3Xhp6Kd70g@mail.gmail.com>
Subject: Re: httpd 2.4.1 and mod_slotmem_shm / mod_proxy_balancer (AH01179)
From: Tom Evans <tevans.uk@googlemail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 7, 2012 at 9:39 AM, Zisis Lianas <Zisis.Lianas@consol.de> wrote:
> Hi Jim,
>
> for me/us it's needed, because we operate with multi-instancing.
>
> e.g.:
> Apache installation directory ("ServerRoot") is /opt/http-2.4.x/
> (belonging to apache:apache). This installation only provides the
> httpd binaries/modules.
>

ServerRoot does not have to be the directory above {bin,libexec,sbin}.
It should be the directory above {conf,logs}.

When running in this scenario, you do have to have absolute paths to
your apache modules, eg:

LoadModule status_module /usr/local/libexec/apache22/mod_status.so

rather than:

LoadModule status_module libexec/apache22/mod_status.so

The disadvantage of doing it this way is that you have to specify full
paths to all your modules. The disadvantage of doing it your way is
that your ServerRoot is not your ServerRoot...

Cheers

Tom