In the past (15 years ago) I installed mod_perl and forgot about it. Iset up my perl cgi script handler to be mod_perl in httpd.conf, and theonly real effect it had on my development cycle was I often had torestart Apache to get it to notice I had changed a script.

These days I am more ambitious and am returning to Web programming aftera long break.

I expect mod_perl to still be useful to cut the overhead of startingPerl. I expect a high throughput this time around, each request will beworth very little to me so I want lots and lots of requests. SO far sogood.

Search Discussions

Perrin HarkinsHi Worik, Your ErrorLog question isn't really a mod_perl issue, but I'd suggest you check for warnings at startup. You may not have APACHE_LOG_DIR defined, etc. I don't use Apache2::Directive, so I can't vouch for it. I prefer simpler things like PerlSetVar. There is an automated test for this though: http://cpansearch.perl.org/src/PHRED/mod_perl-2.0.8/t/response/TestApache/conftree.pm I'd suggest doing some more basic debugging, e.g. use Data::Dumper; print Dumper $tree->as_hash; - Perrin

In the past (15 years ago) I installed mod_perl and forgot about it. Iset up my perl cgi script handler to be mod_perl in httpd.conf, and theonly real effect it had on my development cycle was I often had torestart Apache to get it to notice I had changed a script.

These days I am more ambitious and am returning to Web programming aftera long break.

I expect mod_perl to still be useful to cut the overhead of startingPerl. I expect a high throughput this time around, each request will beworth very little to me so I want lots and lots of requests. SO far sogood.

Worik StantonThe ErrorLog issue only happens under mod_perl. Given that all logs were in the appropriate directory but I went and checked and it is set appropriately in apache2/envvars. If you look at the snippet of my configuration file you will see I set the error log just before setting up mod_perl. Thank you that is useful. I will look into that. I have gotten that file. Is there some documentation to go with it? Thank you. That is helpful too. cheers Worik -- The only true evil is turning people into

Your ErrorLog question isn't really a mod_perl issue, but I'd suggestyou check for warnings at startup. You may not have APACHE_LOG_DIRdefined, etc.

The ErrorLog issue only happens under mod_perl. Given that all logswere in the appropriate directory but I went and checked and it is setappropriately in apache2/envvars. If you look at the snippet of myconfiguration file you will see I set the error log just before settingup mod_perl.

In the past (15 years ago) I installed mod_perl and forgot about it. Iset up my perl cgi script handler to be mod_perl in httpd.conf, and theonly real effect it had on my development cycle was I often had torestart Apache to get it to notice I had changed a script.

These days I am more ambitious and am returning to Web programming aftera long break.

I expect mod_perl to still be useful to cut the overhead of startingPerl. I expect a high throughput this time around, each request will beworth very little to me so I want lots and lots of requests. SO far sogood.

Worik StantonOn another matter... I have not used this testing frame work before (other than watch tests go by during the build process). I looked up http://perl.apache.org/docs/general/testing/testing.html but there does not seem to be a tutorial to get started. Where is the documentation that shows how to arrange the files and run these tests? I tried creating a directory t/ and t/TestApache and put conftree.pm into TestApache and created a file contree.pl which used TestApache::conftree (I had to add a

Worik StantonI am randomly thrashing around trying to get started with the mod_perl API. More accurately I was. I have my bearings now and am making some progress. I have used the API today to get document_root (thank-you [email protected] ) and to filter by IP. cheers Worik -- The only true evil is turning people into things.... Granny Weatherwax [email protected] 021-1680650, (03) 4821804 Aotearoa (New Zealand)

In the past (15 years ago) I installed mod_perl and forgot about it. Iset up my perl cgi script handler to be mod_perl in httpd.conf, and theonly real effect it had on my development cycle was I often had torestart Apache to get it to notice I had changed a script.

These days I am more ambitious and am returning to Web programming aftera long break.

I expect mod_perl to still be useful to cut the overhead of startingPerl. I expect a high throughput this time around, each request will beworth very little to me so I want lots and lots of requests. SO far sogood.