Backing out a mod_perl install
I'm upgrading mod_perl on a Solaris 2.6 production machine. Although a little downtime on this machine won't be a big issue, I'm wondering about backup plans. I've got mod_perl ready for "make install" (I'm currently using a PERL5LIB environment to test mod_perl on a high port from the blib). So I was just going to bring down the server, make install, and then startup the new server. But, I'd like to be able to back out, just in case. I was thinking about tar'ing up the Apache name space, and Apache.pm to backout the Perl modules so I could run the old httpd, if needed. Is that a reasonable thing to do, and if so, is there anything else you would suggest? Thanks, Bill Moseley mailto:[EMAIL PROTECTED]
RE: Backing out a mod_perl install
> -Original Message- > From: Bill Moseley [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 06, 2001 3:18 PM > To: [EMAIL PROTECTED] > Subject: Backing out a mod_perl install > > > I'm upgrading mod_perl on a Solaris 2.6 production machine. > Although a > little downtime on this machine won't be a big issue, I'm > wondering about > backup plans. > > I've got mod_perl ready for "make install" (I'm currently > using a PERL5LIB > environment to test mod_perl on a high port from the blib). > > So I was just going to bring down the server, make install, and then > startup the new server. But, I'd like to be able to back out, just in > case. I was thinking about tar'ing up the Apache name space, > and Apache.pm > to backout the Perl modules so I could run the old httpd, if needed. you can try the tar_Apache and offsite_tar arguments to make and see if they wrap up everything you need... HTH --Geoff
RE: Backing out a mod_perl install
someone please correct me but: I believe that make install will only overwrite httpd (the executable binary). Any other files that already exist will not be touched. Last time I did something like this, I simply made a copy of my httpd binary and everything else was in my system backups. -Original Message- From: Geoffrey Young [mailto:[EMAIL PROTECTED]] Sent: Monday, August 06, 2001 3:21 PM To: 'Bill Moseley'; [EMAIL PROTECTED] Subject: RE: Backing out a mod_perl install > -Original Message- > From: Bill Moseley [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 06, 2001 3:18 PM > To: [EMAIL PROTECTED] > Subject: Backing out a mod_perl install > > > I'm upgrading mod_perl on a Solaris 2.6 production machine. > Although a > little downtime on this machine won't be a big issue, I'm > wondering about > backup plans. > > I've got mod_perl ready for "make install" (I'm currently > using a PERL5LIB > environment to test mod_perl on a high port from the blib). > > So I was just going to bring down the server, make install, and then > startup the new server. But, I'd like to be able to back out, just in > case. I was thinking about tar'ing up the Apache name space, > and Apache.pm > to backout the Perl modules so I could run the old httpd, if needed. you can try the tar_Apache and offsite_tar arguments to make and see if they wrap up everything you need... HTH --Geoff
RE: Backing out a mod_perl install
At 03:21 PM 08/06/01 -0400, Geoffrey Young wrote: >> to backout the Perl modules so I could run the old httpd, if needed. > >you can try the tar_Apache and offsite_tar arguments to make and see if they >wrap up everything you need... Ok, thanks tar_Apache should include all that I need, thanks. I don't see the need for offsite_tar in my case, since I already have mod_perl built and ready for install in the target machine. No need to run make install on the httpd side, right? I can just copy the httpd binary (I'll be using the same ServerRoot as the existing 1.3.12 server), so I'm assuming all my icons and mime.types files from 1.3.12 will be just fine. Bill Moseley mailto:[EMAIL PROTECTED]
packaging mod_perl (was RE: Backing out a mod_perl install)
On Mon, 6 Aug 2001, Bill Moseley wrote: > At 03:21 PM 08/06/01 -0400, Geoffrey Young wrote: > >> to backout the Perl modules so I could run the old httpd, if needed. > > > >you can try the tar_Apache and offsite_tar arguments to make and see if they > >wrap up everything you need... > > Ok, thanks tar_Apache should include all that I need, thanks. I don't see > the need for offsite_tar in my case, since I already have mod_perl built > and ready for install in the target machine. I think that even a better solution is build some RPM/deb/whatever package and take a benefit of the features provided by the packaging systems. Anybody wants to write 'make rpm', 'make deb' so these can be part of the Makefile.PL and other distros using these to create their packages? I think both Mandrake and RH have /usr/lib/rpm/cpanflute, which converts any CPAN tar.gz into src.rpm automatically, which is very cool, since mod_perl is just a CPAN tar.gz. You probably all know that we have a new Apache-Test framework in mod_perl 2.0, so any Apache:: module can easily use it to test its features using the real mod_perl server. How about starting Apache-Dist framework, and write a number of modules that will create Apache::Dist::RPM, Apache::Dist::PPM, Apache::Dist::DEB, ...? Then various bundles Apache::Dist::Bundle::Dev, Apache::Dist::Bundle::Prod, you name it. The system can create packages with Apache/mod_perl/other modules. and then nicely package them into whatever packaging system you prefer, including making packages for off-site distribution and similar. Anybody with good working knowledge of various packaging systems wants to start working on this cool project, which will make mod_perl even more accessible and ubiquitous. Probably most of you don't know but Apache folks have embraced the perl Apache-Test framework to use for the httpd regression testing. If we create Apache-Dist, I think it can be used for httpd and other ASF projects as well. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/ http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
