[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    Re: Best practices for returning 404/file-not-found pages inside
From:       Mark Stosberg <mark () summersault ! com>
Date:       2008-04-29 21:23:42
Message-ID: 20080429172342.5b2e3946 () summersault ! com
[Download RAW message or body]

On Fri, 25 Apr 2008 16:38:36 +0200
André Warnier <aw@ice-sa.com> wrote:

> Mark Stosberg wrote:
> >> Sorry Mark, I misread your mail.  I thought you were using
> >> PerlSetVar. What are you doing exactly?  PerlSetEnv PERL5LIB?
> > 
> > Exactly.
> > 
> Hi guys,
> sorry to butt in, particularly since much higher-grade specialists
> have been in this thread before, but ..
> I seem to recall an earlier thread talking about the same kind of
> thing. Isn't it too late, once the Apache server has started and
> initialised Perl interpreters and so on, to set the environment var.
> PERL5LIB via PerlSetEnv ?
> Would that not explain the curious behaviour seen ?

Possibly. As I  reviewed other environments that are working for us,
I see that we use "SetEnv" there. I just introduced "PerlSetEnv" recently,
as part trying to debug mod_perl problems. 

I did find and change this section in my startup script which seems like 
it could be related:

-    chdir dirname(__FILE__);
-    use lib '../config', '../perllib';

+    my $dir = dirname(__FILE__);
+    use lib $dir.'/../config'; $
+    use lib $dir.'/../perllib';

####

So, I was adding relative paths to @INC before, and now I'm adding absolute ones. 

   Mark

-- 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . 
   Mark Stosberg            Principal Developer  
   mark@summersault.com     Summersault, LLC     
   765-939-9301 ext 202     database driven websites
 . . . . . http://www.summersault.com/ . . . . . . . .


[prev in list] [next in list] [prev in thread] [next in thread]