Geoffrey Young wrote:
So it'll look like:
[warning] setting ulimit to allow core files
ulimit -c unlimited;
/home/stas/perl/5.8.1-ithread-nouseshrplib/bin/perl5.8.1 t/TEST
-trace=debug
[debug] isolated httpd_info VERSION = Apache/2.0.49-dev
[...]
[crit] generating conf/httpd.conf
that's really a c
> So it'll look like:
>
> [warning] setting ulimit to allow core files
> ulimit -c unlimited;
> /home/stas/perl/5.8.1-ithread-nouseshrplib/bin/perl5.8.1 t/TEST
> -trace=debug
> [debug] isolated httpd_info VERSION = Apache/2.0.49-dev
> [...]
> [crit] generating conf/httpd.conf
that's really a cri
Geoffrey Young wrote:
Stas Bekman wrote:
I find that users get confused about the various tracing codes used by
A-T, since it's not necessarily clear what all these '&&&', '***', '!!!'
prefices mean and how to tell which ones are crucial errors and which
ones aren't. So I suggest to just print the
Stas Bekman wrote:
> I find that users get confused about the various tracing codes used by
> A-T, since it's not necessarily clear what all these '&&&', '***', '!!!'
> prefices mean and how to tell which ones are crucial errors and which
> ones aren't. So I suggest to just print the level ala Ap
I find that users get confused about the various tracing codes used by A-T,
since it's not necessarily clear what all these '&&&', '***', '!!!' prefices
mean and how to tell which ones are crucial errors and which ones aren't. So I
suggest to just print the level ala Apache log messages, e.g.:
