Two instances of Apache on the same server

[Tom Goren]

Gotcha - just seems to me the extra few bucks with the VPS provider (most
likely applicable to the scenario you depicted) would be less than the
effort to create such a beast.

>From my minimal googling, and from some experience with apache it would
require compiling apache twice with different ./configure options, and then
perhaps doing some editing of the init scripts as well.

That means more than a few developer hours - based on around 60$ an hour for
a developer worthy of the project - you could get a linode vps for a year
for that kind of cash.

Tom.



On Wed, Oct 6, 2010 at 12:53 PM, Amos Shapira <amos.shapira at gmail.com>wrote:

> 2010/10/6 Tom Goren <tom at tomgoren.com>:
> > Sorry for the crude question, but why would you want to do this?
> > Are you trying to run to different versions of apache for testing or for
> > some specific application need?
> > What advantages do two separate instances of the actual apache process
> > present over a multiple virtual host configurations? This usually covers
> 99%
> > of usage cases.
> > Just curious,
>
> I'm not the original poster but I could envision a use for this on our
> systems - e.g. most of our web servers can work with Apache Worker MPM
> but one of them has a compiled apache module which can only work with
> the Prefork MPM. If we had to run all of them on the same OS image
> (e.g. as a small appliance or a private development environment) then
> I think such a trick would be useful to us.
>
> --Amos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20101006/58318326/attachment.html>