in reply to Profiling under mod_perl

I've never heard of anyone trying to do this with -C before. Just add it to your config file. I'm not sure it will work ouutside of a specific Location block. There is some documentation here.

Replies are listed 'Best First'.
Re^2: Profiling under mod_perl
by aufflick (Deacon) on Feb 21, 2005 at 23:52 UTC
    Nope - tried that. No dice...

    I suspect that my mason handler is connecting to mod_perl higher (or earlier - depending on your mental model) and thus is being excluded as part of the startup.

      Put this in your httpd.conf before anything else that loads a perl module:
      <Perl> require Apache::DB; Apache::DB->init; </Perl>
        Hmm - it seems like a good suggestion, since that's how you initialise running apache through the perl debugger (plus you add PerlFixupHandler Apache::DB of course...) and the profiling code uses the same debugger hooks.

        But when I do that combined with PerlModule Apache::DProf Apache actually exits (with no error) on the first request...