in reply to Getting mod_perl to actually 'activate'..

Is this a case where you run the first script from the command line, but run the other page from a server (presumably apache) context? If so, then you are probably running into a common problem. The script that is failing is running in the context of the web server. It may not be running with the user, environment, nor pwd that you expect.
  • Comment on Re: Getting mod_perl to actually 'activate'..

Replies are listed 'Best First'.
Re^2: Getting mod_perl to actually 'activate'..
by MashMashy (Sexton) on Feb 16, 2009 at 16:04 UTC
    Can you be more specific in your answer? I'm afraid I don't understand your answer enough to even look into where to go next.
[reply]
      OK, you have 2 scripts in your example. The first demonstrates that your ENV is what you desire. My question was, are you running that test script from the command line? I assume you are running the latter script from within a web server. When the web server runs a script it does so from within the context of the web server. This context is usually done with the environment of the web server, using the web server' user name. This may not be what you expect.
[reply]
        Correct, that script is being run by http request from an external browser. internal "perl whatever.html" tests do not show the GATEWAY_INTERFACE or the MOD_PERL environment, when run as root and/or user. Is this significant?
[reply]

In Section Seekers of Perl Wisdom