The apache part isn't the problem. I can easily run on different ports, and whatnot. In fact, both apache's are working fine independantly, so it's just the perl / mod_perl issue. When I do a "make install" of mod_perl 2.x I don't want mod_perl 2 based perl modules tromping all over the existing mod_perl 1.3 system install.
Both my apache 1.3 and 2.2 installs are custom compiled into apache standard /usr/local/apache / /usr/local/apache2 trees (instead of using the hatchet job versions that redhat likes to ship.) The deal here is that the customer is migrating from an apache 1.3 setup to an apache 2.2 setup and only has one machine available in the colo. Adding another is not feasable at the moment. On Tue, May 15, 2007 at 03:47:19PM -0400, John Saylor said: > hi > > ouch. > > the only suggestion i have is to reasess your needs. really- you'll > spend at least 10 hours dicking around with the network config to say > nothing about httpd.conf. if you get paid over $10. and hour, that makes > it worth it buy a new machine. > > -----Original Message----- > From: Walt Reed [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 15, 2007 3:39 PM > [deletions] > I have a need to install both apache 1.3.x / mod_perl 1.x and apache > 2.2.x / mod_perl 2.x on the same machine. > >
