On Mon, 16 Jul 2001, Stas Bekman wrote:
you can end up with a long file with various PerlTrace settings. Instead
of scrolling back and forth and remembering what bits very set before, why
not just switching off the unwanted bits?
i guess this is what i'm having trouble seeing. personally i
On Fri, 13 Jul 2001, Doug MacEachern wrote:
On Sat, 30 Jun 2001, Stas Bekman wrote:
modperl_trace_level_set gets called from modperl_cmd.c only if you have
PerlTrace in httpd.conf. Of course this case ignores the env var, but
there is no other place in the code that calls this func to
On Sat, 30 Jun 2001, Stas Bekman wrote:
modperl_trace_level_set gets called from modperl_cmd.c only if you have
PerlTrace in httpd.conf. Of course this case ignores the env var, but
there is no other place in the code that calls this func to check for the
env setting of MOD_PERL_TRACE.
modperl_trace_level_set gets called from modperl_cmd.c only if you have
PerlTrace in httpd.conf. Of course this case ignores the env var, but
there is no other place in the code that calls this func to check for the
env setting of MOD_PERL_TRACE.
On the related note the following would be very
