Re: Both mod_perl 1 and 2 on same machine
On 5/22/07, Roger McCalman <[EMAIL PROTECTED]> wrote: On Tue, May 22, 2007 at 09:20:17PM +0200, Vetle Roeim wrote: > On 5/15/07, Walt Reed <[EMAIL PROTECTED]> wrote: > > > >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. > > > >Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but > >that option no longer exists in current versions of mod_perl 2. > > > >Didn't see anything obvious in the install manual either. > > > >Suggestions? > > VMWare FreeBSD jail's Linux chroot's I run several different FreeBSD jails on a single server that have defferent apache/perl/php/postgres etc in. Some are projects that were built on from FreeBSD 3/4 and run on a FreeBSD 5.x server. Works very well with very little overhead. Not really any reason to do anything that esoteric. Change the Perl library paths in Apache's config files using ModPerl 1 on 1.3 and 2 on 2.x, run Apache 1 and 2 on different ports, and you're good. Stephan
Re: Both mod_perl 1 and 2 on same machine
On Tue, May 22, 2007 at 09:20:17PM +0200, Vetle Roeim wrote: > On 5/15/07, Walt Reed <[EMAIL PROTECTED]> wrote: > > > >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. > > > >Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but > >that option no longer exists in current versions of mod_perl 2. > > > >Didn't see anything obvious in the install manual either. > > > >Suggestions? > > VMWare FreeBSD jail's Linux chroot's I run several different FreeBSD jails on a single server that have defferent apache/perl/php/postgres etc in. Some are projects that were built on from FreeBSD 3/4 and run on a FreeBSD 5.x server. Works very well with very little overhead. Cheers, Roger
Re: Both mod_perl 1 and 2 on same machine
On 5/22/07, Vetle Roeim <[EMAIL PROTECTED]> wrote: VMWare Total overkill, and the performance hit is not worth it. Even my suggestion of separate perl installs is overkill unless you need to use a CPAN module that doesn't play well with both installed. - Perrin
Re: Both mod_perl 1 and 2 on same machine
On 5/15/07, Walt Reed <[EMAIL PROTECTED]> wrote: 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. Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but that option no longer exists in current versions of mod_perl 2. Didn't see anything obvious in the install manual either. Suggestions? VMWare -- Vetle Roeim
Re: Both mod_perl 1 and 2 on same machine
On Tuesday 15 May 2007 22:33, Walt Reed wrote:
> I would prefer however to put all my test modules for this migration in the
> /usr/local/apache2/perllib space, but looking at the mod_perl configure
> options, I didn't see which option specified this... MP_AP_PREFIX?
> MP_AP_DESTDIR? Neither one of those looked appropriate.
BASE=/path/to/somewhere
PERLV=$(perl -e 'printf "%vd", $^V')
make \
INSTALLSITEARCH=$BASE/$PERLV/i586-linux-thread-multi \
INSTALLSITELIB=$BASE/$PERLV \
INSTALLSITEBIN=$BASE/usr/bin \
INSTALLSCRIPT=$BASE/usr/bin \
INSTALLSITEMAN1DIR=$BASE/man/man1 \
INSTALLSITEMAN3DIR=$BASE/man/man3 \
install
Then in the httpd.conf:
PerlSwitches -I${BASE}
I do something like this in RPM builds. So I have httpd and mod_perl bundled
in /opt/apache, /opt/apache22 etc. Apache is located in /opt/apache and
mod_perl in /opt/apache/mod_perl.
This is a bit cumbersome because you have to look out in which tree to install
additional modules. But for me it works.
Torsten
pgp5MXm5XdSK2.pgp
Description: PGP signature
Re: Both mod_perl 1 and 2 on same machine
Modify @INC to only load the libraries you need, and make sure to install the MP1 modules in a different location than the MP2 ones. Basically, install the 'default' server perl modules normally, and install the 'other' ones in a special directory that you then modify @INC to include through use lib () or direct manipulation of @INC in a begin block. -- Dodger Walt Reed wrote: 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.
Re: Both mod_perl 1 and 2 on same machine
On Tue, May 15, 2007 at 04:05:38PM -0400, Michael Peters said: > Walt Reed wrote: > > 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. > > They shouldn't tromp over anything. All mod_perl2 modules are in the Apache2 > namespace. Now, this doesn't guarantee that some 3rd party module won't detect > that you're running under mod_perl by trying to use 'Apache2' instead of > looking > at $ENV, but that's a different story... OK, that is exactly what I needed to know. So no big conflicts then in perl module land having both installed... I would prefer however to put all my test modules for this migration in the /usr/local/apache2/perllib space, but looking at the mod_perl configure options, I didn't see which option specified this... MP_AP_PREFIX? MP_AP_DESTDIR? Neither one of those looked appropriate. Other perl modules are easy with PREFIX and LIB.
Re: Both mod_perl 1 and 2 on same machine
On May 15, 2007, at 4:05 PM, Michael Peters wrote: Walt Reed wrote: 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. They shouldn't tromp over anything. All mod_perl2 modules are in the Apache2 namespace. Now, this doesn't guarantee that some 3rd party module won't detect that you're running under mod_perl by trying to use 'Apache2' instead of looking at $ENV, but that's a different story... Doesn't the mp2 installation require the removal of all mp1/mp2 versions before the namespace renaming ?: // Jonathan Vanasco | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | SyndiClick.com | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Re: Both mod_perl 1 and 2 on same machine
On May 15, 2007, at 3:49 PM, Perrin Harkins wrote: My approach would be to install two copies of perl, and put one of them on each. Or, install each in a local perl lib directory rather than the system dir. (Local installs of CPAN modules are well-covered elsewhere.) I'd second the latter suggestion -- 2 separate local installs for all apache/mp related CPAN modules. I'd also remove the /Apache and /Apache2 directories and touch them as flat files -- just to make sure no one can accidentally install files in them. your requirements are likely to cause you a ton of headaches in the future -- best now to plan ahead and minimize them // Jonathan Vanasco | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | SyndiClick.com | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Re: Both mod_perl 1 and 2 on same machine
Walt Reed wrote: > 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. They shouldn't tromp over anything. All mod_perl2 modules are in the Apache2 namespace. Now, this doesn't guarantee that some 3rd party module won't detect that you're running under mod_perl by trying to use 'Apache2' instead of looking at $ENV, but that's a different story... -- Michael Peters Developer Plus Three, LP
Re: Both mod_perl 1 and 2 on same machine
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. > >
Re: Both mod_perl 1 and 2 on same machine
Walt Reed wrote: 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. Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but that option no longer exists in current versions of mod_perl 2. Didn't see anything obvious in the install manual either. Suggestions? I have a couple machines with multiple versions of apache and mod_perl. A front end proxy apache22 installed from ports, and source install of apache13+mod_perl in /usr/local/apache-perl and a source install of apache22+mod_perl2 in /usr/local/apache22-perl. I only have one version of perl and haven't had any problems. -Glenn
Re: Both mod_perl 1 and 2 on same machine
On 5/15/07, Walt Reed <[EMAIL PROTECTED]> wrote: 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. [...] Suggestions? My approach would be to install two copies of perl, and put one of them on each. Or, install each in a local perl lib directory rather than the system dir. (Local installs of CPAN modules are well-covered elsewhere.) - Perrin
RE: Both mod_perl 1 and 2 on same machine
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.
Both mod_perl 1 and 2 on same machine
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. Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but that option no longer exists in current versions of mod_perl 2. Didn't see anything obvious in the install manual either. Suggestions?
