Single process mode is usually started by calling httpd with a -X parameter. If you don't see warn output in the error_log, it's either not getting to your warn statement or you're looking in the wrong error_log. You might be interested in this book, which you can read on-line or buy on paper. | [reply] |
> Single process mode is usually started by calling httpd with a -X parameter
This I know, but on Windows apache is controlled as service. Any idea how to tell the service to run a single mode?
> If you don't see warn output in the error_log, it's either not getting to your warn statement
package Apache2::Hello;
use strict;
use warnings;
use Apache2::RequestRec(); # for $r->content_type
use Apache2::RequestIO(); # for $r->puts
use Apache2::Const qw/:common/;
use Apache2::Reload;
sub handler {
my $r = shift;
my $time = scalar localtime();
my $package = __PACKAGE__;
$r->content_type('text/html');
warn 'darn';
$r->puts(<<"END");
<HTML><BODY>
<H3>Hello</H3>
Hello from <B>$package</B>! The time is $time.
</BODY></HTML>
END
return Apache2::Const::OK;
}
1;
You think?
> or you're looking in the wrong error_log
There is only one I know. Configured by ErrorLog parameter in httpd.conf
Besides, die messages go there as they should.
Thanks,
Artem. | [reply]
[d/l] |
| [reply] |
| [reply] |