Re^3: Getting mod_perl to actually 'activate'..

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.

Comment on Re^3: Getting mod_perl to actually 'activate'..

Replies are listed 'Best First'.
Re^4: Getting mod_perl to actually 'activate'.. by MashMashy (Sexton) on Feb 16, 2009 at 16:52 UTC
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]
Re^5: Getting mod_perl to actually 'activate'.. by MashMashy (Sexton) on Feb 16, 2009 at 16:54 UTC
and, there is only one script there -at least, from how I think you are getting at it) - the .html file, with the ENV printout. The second (.conf) is the httpd.conf, run only when apache is started.	[reply]
Re^5: Getting mod_perl to actually 'activate'.. by Illuminatus (Curate) on Feb 16, 2009 at 17:40 UTC
You still have not answered my question. You have defined 2 scripts. The first one at the top of the post. Is the one you are you running from the *nix prompt? If so, you are running it with the user and environment of your shell prompt. In the apache server, the script runs as the apache user (which I believe you can set somewhere in the apache configuration). I am not sure, but you might be able to set the environment for when scripts are run from within the apache config as well.	[reply]