<div dir="ltr">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.<div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>Tom.</div>
<div><br></div><div><br><br><div class="gmail_quote">On Wed, Oct 6, 2010 at 12:53 PM, Amos Shapira <span dir="ltr"><<a href="mailto:amos.shapira@gmail.com">amos.shapira@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2010/10/6 Tom Goren <<a href="mailto:tom@tomgoren.com">tom@tomgoren.com</a>>:<br>
<div class="im">> Sorry for the crude question, but why would you want to do this?<br>
> Are you trying to run to different versions of apache for testing or for<br>
> some specific application need?<br>
> What advantages do two separate instances of the actual apache process<br>
> present over a multiple virtual host configurations? This usually covers 99%<br>
> of usage cases.<br>
> Just curious,<br>
<br>
</div>I'm not the original poster but I could envision a use for this on our<br>
systems - e.g. most of our web servers can work with Apache Worker MPM<br>
but one of them has a compiled apache module which can only work with<br>
the Prefork MPM. If we had to run all of them on the same OS image<br>
(e.g. as a small appliance or a private development environment) then<br>
I think such a trick would be useful to us.<br>
<font color="#888888"><br>
--Amos<br>
</font></blockquote></div><br></div></div>