perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Reppucci <...@logsoft.com>
Subject Re: Influencing @INC list
Date Tue, 12 Feb 2002 03:29:42 GMT

OK, I'll be the one to throw out the gratuitous plug for Geoff,
etal's book. The Mod_Perl Cookbook has a nice discussion of exactly
this in Chapter 2. (I'd give you the page, but I left it at work...)

(I'm only through the first few chapters, but from what I've read so
far, this is a real winner.  Buy it.)

<Steve>

On Mon, 11 Feb 2002, Brian Reichert wrote:

> On Mon, Feb 11, 2002 at 04:29:43PM -0500, Kevin Slean wrote:
> >
> > Mod Perl Mongers...
> >
> > I need to run multiple apache servers on one Solaris 2.7 box configured in
> > such a way that each of them accesses their own private copy of perl
> > libraries.  I would like to achieve this configuration with the
> > least amount of changes to my over all implementation.
> >
> > For instance, given 2 apache servers defined in the following 2 directories:
> >
> >    /usr/local/siteA   <- directory tree containing everything for server A
> >    /usr/local/siteB   <- directory tree containing everything for server B
> >
> > The default perl installation on this unix system is under
> > /usr/local/lib/perl5 and the default @INC list is:
>
> I believe you can abuse PERL5LIB in each vhost...
>
> >
> > Kevin
> >
>
>

-- 
Steve Reppucci                                       sgr@logsoft.com |
Logical Choice Software                          http://logsoft.com/ |
=-=-=-=-=-=-=-=-=-=-  My God!  What have I done?  -=-=-=-=-=-=-=-=-=-=


Mime
View raw message