Re: difference between PerlSetEnv and $ENV{}= ?

PM, Torsten Förtsch wrote: > On Tuesday, 27 March 2012 12:48:01 Charlie Katz wrote: > > Still, can someone explain why > > > >PerlSetEnv ENV_VAR /my/value > > > > has different effects than > > > > > >$ENV{ENV_VAR} = '/my/valu

Re: difference between PerlSetEnv and $ENV{}= ?

> Do the PerlSetEnv as you are, and use this module to ensure it is visible > from your pgplot lib env. > > ** ** > > http://search.cpan.org/dist/Env-C/C.pm > > ** ** > > ** ** > > *From:* ckatz...@gmail.com [mailto:ckatz...@gmail.com] *On Behalf Of *Charlie >

Re: difference between PerlSetEnv and $ENV{}= ?

I have also tried using SetEnv from mod_env, and neither the Perl nor the PGPLOT library can see the environment variable set that way. On Mon, Mar 26, 2012 at 2:54 PM, Randolf Richardson wrote: > > Hi, > > > > My web app uses the PGPLOT module to access PGPLOT, which is a scientific > > plotting

difference between PerlSetEnv and $ENV{}= ?

Hi, My web app uses the PGPLOT module to access PGPLOT, which is a scientific plotting library commonly used in my field. It is a Fortran library, with a C wrapper around it, which is then wrapped in Perl. This works fine in my test scripts, producing the desired graphics. The library requires

$r vs. Apache2::RequestUtil->request

ne help me understand this difference, and how to use the object retrieved from A::RU::request to access the Apache2::Log methods? Why isn't the original $r an Apache2::RequestRec object? This is Perl 5.14.2, mod_perl 2.0.5 Thanks. Charlie Katz

Re: $r vs. Apache2::RequestUtil->request

. On Tue, Oct 25, 2011 at 1:43 PM, Charlie Katz wrote: > Hi, I'm confused about something. I am cleaning up some legacy Perl code > in our application, and I find a number of our custom Perl modules have > functions which require $r be passed to them solely for use in logging (e.g. &g

Re: intermittent import errror from Apache2::RequestUtil

:RequestUtil, and methods aren't exported, they're invoked on instances of the class. Duh. > HTH > > --Geoff SD (sure does) Out of curiosity, why would my mistake not cause an error every time it runs? Thanks! Charlie Katz Harvard-Smithsonian Center for Astrophysics [EMAIL PROTECTED]

intermittent import errror from Apache2::RequestUtil

erl 5.8.5; also Mason 1.33) Thanks. Charlie Katz Harvard-Smithsonian Center for Astrophysics [EMAIL PROTECTED]

Re: "Insecure dependency in eval while running setgid" error

t/reinstalled/restarted, and the EGID problem is gone. I checked the 2.0.3 source and found this already fixed there. Sagar, can you try the same thing with your server? Perhaps the "tainting" problem will just disappear once this bug is fixed. Regards, Charlie -- Charlie Katz Harvard-Smithsonian Center for Astrophysics [EMAIL PROTECTED]

Re: "Insecure dependency in eval while running setgid" error

Hi, I recently ran into a similiar situation, which I asked about on this list (message subject "inconsistent taint check results"). Do you by any chance "use Taint;" (Taint-0.09) ? I found that when I stopped using that, the problem went away. Just a guess. Regard

Re: inconsistent taint check results

ready there. Let that be a lesson to me. ;-) Charlie Katz On Wednesday 07 March 2007 12:27 pm, Charlie Katz wrote: > Hi all, > > The site I develop (Apache 2.2.3, mod_perl 2.0.2 [perl 5.8.5], Mason 1.33) > runs with taint checking ("PerlSwitches -wT -I/www"). It's be

inconsistent taint check results

h!). I'm afraid I have little idea of what to do next. Any suggested courses of inquiry I could take up would be greatly appreciated. Regards, Charlie -- Charlie Katz Harvard-Smithsonian Center for Astrophysics [EMAIL PROTECTED]

Re: use mod_info and mod_status via mod_perl?

uot; > > there?  Hmm... > > Yes. SetHandler sets the response handler not anything else. > As long as your auth* is in modules that will work as PerlAuth*Handlers > then you're good to go. Alright then. I just knew I was missing something simple. Thanks for the help. Cha

Re: use mod_info and mod_status via mod_perl?

t one can't use Perl*Handler directives unless using "SetHandler perl-script". Can I still set a PerlAuth*Handler in a if I have "SetHandler server-status" there? Hmm... Charlie On Tuesday 22 August 2006 3:44 pm, you wrote: > Charlie Katz wrote: > >

Re: use mod_info and mod_status via mod_perl?

On Tuesday 22 August 2006 3:37 pm, Charlie Katz wrote: > > SetHandler server-status > ... > Allow from ... > > > doesn't work for me because I don't want to control access based on URI, > but rather the custom authorization level my site assigns when a use

use mod_info and mod_status via mod_perl?

$r->lookup_uri(''); $subr->handler('server-status'); $subr->run; This seems straightforward enough (and it works), but I am bothered by using lookup_uri() when I don't actually care what the URI is. Is there a more direct way to do what I want? Regards, Charlie