Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
That's a good point. I will at least suggest it to them. Scott On Tue, 2005-04-19 at 17:37 -0400, Perrin Harkins wrote: > On Tue, 2005-04-19 at 17:21 -0400, Scott Cain wrote: > > That is a great idea and I will use it in the future. Unfortunately, it > > doesn't really help my users who, while

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
Philip, Thanks! That is very useful info--I will forward it to the turnkey developers (it's not my project, just related to one I am working on). Scott On Tue, 2005-04-19 at 17:26 -0400, Philip M. Gollucci wrote: > Scott Cain wrote: > > >I am using turnkey (http://turnkey.sf.net) which tries t

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Perrin Harkins
On Tue, 2005-04-19 at 17:21 -0400, Scott Cain wrote: > That is a great idea and I will use it in the future. Unfortunately, it > doesn't really help my users who, while very bright, are not perl > developers and would likely balk at doing that. I do something similar to what Cliff has here. Ther

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Philip M. Gollucci
Scott Cain wrote: I am using turnkey (http://turnkey.sf.net) which tries to do some fancy footwork to determine which mod_perl is being used: (note that Turnkey::Root::mod_perl_version parses $ENV{MOD_PERL} and returns 2 if it looks like mod_perl 1.99+ or 1 otherwise): Thats not going to run und

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
That is a great idea and I will use it in the future. Unfortunately, it doesn't really help my users who, while very bright, are not perl developers and would likely balk at doing that. Thanks, Scott On Tue, 2005-04-19 at 14:14 -0700, ___cliff rayman___ wrote: > Scott Cain wrote: > > >because I

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
I am using turnkey (http://turnkey.sf.net) which tries to do some fancy footwork to determine which mod_perl is being used: (note that Turnkey::Root::mod_perl_version parses $ENV{MOD_PERL} and returns 2 if it looks like mod_perl 1.99+ or 1 otherwise): if (Turnkey::Root::mod_perl_version( $ENV{MOD

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread ___cliff rayman___
Scott Cain wrote: because I had to blow away my installation of mp1 to get my mp2 apps to work. I always build my servers with their own copy of perl in a directory such as: /usr/local/httpd_20050419 I build a fresh perl and apache in that directory, and get everything working. My particular

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Philip M. Gollucci
Scott Cain wrote: I did see the rename doc, though I didn't realize that it applied to something as recent as the transition to RC4->RC5. Are you currently using mp1 and mp2? What about any mp applications that were written prior to this name change? Of course, I can't do any testing myself, be

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
I did see the rename doc, though I didn't realize that it applied to something as recent as the transition to RC4->RC5. Are you currently using mp1 and mp2? What about any mp applications that were written prior to this name change? Of course, I can't do any testing myself, because I had to blo

Re: Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Philip M. Gollucci
Sc So, the question is: is it possible (and relatively easy) to have mod_perl1 and mod_perl2 installed on the same machine? Try mod_perl2.00 RC5 seems to work for me :) MP_APACHE2_INST=1 is gone. mod_perl.pm is installed as mod_perl2.pm and mp2 libs are in Apache2:: directory and namespace by de

Apache1/mp1 and Apache2/mp2 on the same machine

2005-04-19 Thread Scott Cain
Hello, I imagine that this question has been asked before, but my google skills are failing me at the moment. Here's the thing: I have users who would like to keep their apache1/mp1 setup in place while they work on the same machine testing apache2/mp2. When I tried to do a similar thing a month