I've considered doing something similar before, but used 3. one to listen to
port 80 and pass requests off to the other two on different ports using
mod_rewrite. Different ServerRoot's are the important part. You can even
still serve all your pages from one central DocumentRoot.
---
Stop! Whoever crosseth the bridge of Death, must answer first
these questions three, ere the other side he see!
"What is your name?"
"Sir Brian of Bell."
"What is your quest?"
"I seek the Holy Grail."
"What are four lowercase letters that are not legal flag arguments
to the Berkeley UNIX version of `ls'?"
"I, er.... AIIIEEEEEE!"
On Tue, Aug 28, 2001 at 08:51:00AM -0700, Rob Hudson wrote:
> I've compiled apache with built-in PHP. And I've compiled apache with
> built-in mod_perl. And I've compiled apache with both PHP and
> mod_perl built-in. My server mainly does PHP, but I'd like to play
> with mod_perl. The only downside is that if you compile both into
> apache, each apache server that gets spawned, takes up a gob of memory
> b/c it's got both PHP and mod_perl in it's pockets. Looks like it eats
> about 4-5 MB per process.
>
> So, my question is can you have 2 apaches on the same server running
> concurrently? Say, 1 with PHP to handle the main pages. And 1 with
> mod_perl, limited to a couple servers max, as the test apache server.
> Would this just be a matter of having 2 build directories and 2
> install locations? Has anyone done this before?
>
> Thanks,
> Rob
>
> --
> Rob <rob_at_euglug_dot_net>
> my @euglugCode = qw(v+++ e--- eug+ bsd+++ gnu+ S+++);
--
Christopher Maujean IT Director Premierelink Communications
[EMAIL PROTECTED] www.premierelink.com
----------------------------------------------------------------------
GnuPg/PGP: 0x5DE74D38
Fingerprint: 91D4 09FE 18D0 27C1 A857 0E45 F8A4 7858 5DE7 4D38
