On Wed, 6 Sep 2000, Perrin Harkins wrote:
> On Wed, 6 Sep 2000, Bill Moseley wrote:
> > I hope I didn't miss anything in the Guide at install.html and in
> > control.html, but I was looking for any suggestions on upgrading mod_perl
> > and Perl on a running production machine to limit the amount of down time.
>
> We use RPMs. Some form of package, even if it's just a tarball, is a good
> idea. Build it on a different server and then just install it. Having
> multiple servers really comes in handy here because you can take some off
> line, upgrade them while the others are live, and then switch. Then your
> site remains up the whole time.
The problem of the tar-ball is that it doesn't know to cleanup previously
installed files. Imagine a situation where some module that was previously
installed in perl5/5.00503 now installed in perl5/site_perl/5.005 -- You
get the problem where the old version is loaded before the new one.
Therefore tar-ball is not a good solution, unless you scratch the whole
tree a moment before you untar the ball.
_____________________________________________________________________
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://jazzvalley.com
http://singlesheaven.com http://perlmonth.com perl.org apache.org
