Boysenberry Payne wrote:
I'm using an OS X box with MP 1.26 and have striped everything down to a
basic
handler and still get the errors intermittently. Someone on this list
mentioned there
was a known apache 1.3.33/ MP 1.26 bug something to this effect. I've
resigned myself
to being ok with this.
I believe that was me.
After researching a little on Perl Monks someone said it might be
circular references
and suggested I use Data::Dump to see whether I do or not. Another
thing that they
said I could do was put:
warn "Module Name was Destroyed";
in custom DESTROY blocks. I tried it and found some of my modules
weren't being
destroyed properly. I was told I should look at the 'foo' =>
$VAR->{some_scalar} lines
as possible circular loops. There were bunches of them. Which in my
situation is
pretty hard not to do using OOP. I'm going through my code now step by
step and
trying to minimize them, or delete them once they've been used.
What happens if you don't load any of YOUR code and just load mp1 with a
defacto startup.pl file.
Again don't load any of YOUR code.
My question actually comes from the warn "Module Destroyed" statements.
When I start up apache I usually get one on start up. Is this the
parent or root httpd?
Depends, you could fire up gdb and check it out. Though I don't know how that
will pan out on OS X.
% gdb httpd
gdb>run -X -d /path/to/serverroot
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci ([EMAIL PROTECTED]) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
