On Wed, 2005-08-24 at 08:53 -0500, 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.
They don't sound like a real problem, but I don't get them, so I
wouldn't say you have to resign yourself to having them.
> I was told I should look at the 'foo' =>
> $VAR->{some_scalar} lines
> as possible circular loops.
I'm not sure what would be dangerous about that, but I guess there must
be a larger context.
> When I start up apache I usually get one on start up. Is this the
> parent or root httpd?
> Is it normal for it to clean up on start?
When an object goes out of scope, it gets DESTROYed. This isn't the
whole parent process we're talking about, just one object.
> Am I missing an easier way to get my application tightened up?
What are you trying to tighten up? Are you still just trying to get rid
of the warnings on shutdown?
> I haven't noticed my httpd
> processes
> ballooning in memory either, so I should be fine right?
That's the major worry with circular refs, so if you don't see that, you
don't need to worry too much.
> Finally, when does mod_perl do clean up, shut down, each request, or
> both?
The phases of request handling are documented pretty well on the site
and in various mod_perl books. The interpreter won't be shut down until
the process exits, but that may be long before the server is shut down
for a particular process.
- Perrin
