Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> 
> 
>>>Philippe, did you by chance watch the error log when testing that 
>>>change? I guess you did, but not with the worker/threaded mpm. :)
>>
>>
>>
>>I must have been running prefork that time. Sorry, should have caught this.
> 
> 
> no worries, I have the same issue with worker :)
> 
> 
>>>my bug report still didn't make it to p5p. But even when it does I 
>>>doubt anybody is going to look at it. threads support is pretty dead 
>>>at the moment at p5p.
>>
>>
>>Suggest this patch to just move the tied sub declaration to one of the 
>>startup-scripts instead of in a <Perl > block
> 
> 
> +1, plus, i'll add a comment to why this is here, later once we get a perl bug 
> id assigned

Yeah, I was looking around trying to find the perl bug id assigned to
this thing until I realized there wasn't one yet. So I guess I could at
least temporarly link to the bug report p5p. Stas do you have a link to it ?

> 
>>+#For the tied %Location in <Perl > sections
>>+use Tie::Hash;
>>[EMAIL PROTECTED]::PerlSection::ISA = qw(Tie::StdHash);
>>+sub Tie::PerlSection::FETCH {
>>+    my ($hash, $key) = @_;
>>+    if ($key eq '/tied') {
>>+        return 'TIED';
>>+    }
>>+    return $hash->{$key};
>>+}
> 
> 
> Whoah, we are back to the clean log under threaded mpm.

And threaded builds startup in 5 seconds and less for me, yay!

> Randy, is that the case on win32? no leaks/early freeing/etc perl reports?
> 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to