Geoffrey Young wrote:
However open_logs and post_config running 4 times doesn't seem right, and mod_perl has no control over it. Could you try to set a breakpoint in modperl_hook_post_config and look at the traces with an aim to figure out why this happens four times? Remember that apache restarts itself, so 2 times is the right answer.
I've just realized that printing out $$/$tid is not very helpful, since tid doesn't map 1:1 to the perl interpreter, so what we really need is $$/interpreter id, which can easily be done in the tracing C code, but not from the perl code. I'm thinking of providing an accessor to print the current perl interpreter address from the perl code, or is there one already in perl that I don't know about? Some B:: or Devel:: module?
__________________________________________________________________ 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]
