Re: object not being destroyed in a TemplateToolkit-based handler

[Robin Berjon <ro...@knowscape.com>]

At 13:24 08/02/2001 -0500, Vivek Khera wrote:
>Ok... Upgrade to "Apache/1.3.17 (Unix) mod_perl/1.25_01-dev" fixed the
>object destroy issue.  Yay!
>
>Old versions were Apache 1.3.14 and mod_perl 1.24_02-dev.
>
>Why that fixes it, I dunno.  (Nor do I care at this point ;-)

I'm glad your problem is soved, but does anyone have any idea what
triggered that problem ? I'm running 1.3.14/1.24_01 and though I'm not
seeing any serious leakage, I'd rather know what can cause it as I probably
won't be upgrading my production server too soon.

-- robin b.
"Windows may be pretty. And easy. But it has no depth or soul. It's like
the one-night stand of operating systems. You feel cheap after using it."
-- Steph, in User Friendly

Re: Accessing Global Configuration Directives

[sterling <st...@covalent.net>]

not sure quite what you're asking, but if you're looking for a global 
PerlSetVar/PerlAddVar type of thing - well, as of 1.21_01 i believe you
can do it - as long as you have access to Apache::Server.  Like in a child
init handler:



PerlAddVar foo bar
PerlAddVar foo bar2
PerlChildInitHandler myChildInitHandler::init

and then in the init handler do something like

sub init
{
    my $s = shift;
    my @values = $s->dir_config->get('foo');
}

@values will be [bar, bar2]

is that what you're lookin for?

sterling


On Fri, 9 Feb 2001, Stathy Touloumis wrote:

> Is it possible to access a global configuration directive without using the
> request object?
> 
> Thanks,
> 

Accessing Global Configuration Directives

[Stathy Touloumis <st...@edventions.com>]

Is it possible to access a global configuration directive without using the
request object?

Thanks,

Re: object not being destroyed in a TemplateToolkit-based handler

[Vivek Khera <kh...@kciLink.com>]

>>>>> "RB" == Robin Berjon <ro...@knowscape.com> writes:

RB> At 13:24 08/02/2001 -0500, Vivek Khera wrote:
>> Ok... Upgrade to "Apache/1.3.17 (Unix) mod_perl/1.25_01-dev" fixed the
>> object destroy issue.  Yay!

RB> I'm glad your problem is soved, but does anyone have any idea what
RB> triggered that problem ? I'm running 1.3.14/1.24_01 and though I'm not

Actually, it turned out to be an issue with defining a MACRO causing
the stash to not get GC'd by perl.  It is not a mod_perl issue at all.