BEGIN
block time) that the subsequent require did not restore.
When these errors happen the thread may die, which may explain why
several reloads don't work - but eventually you've killed each of the
threads that were running, and the new ones initialize fresh and normal.
David
Pa
cts/wss/install/apache/mason"
PerlSetVar MasonCompRoot
"/home/rutski/Documents/projects/wss/install/apache/htdocs/dynamic"
======
Patrick Rutkowski wrote:
I'm currently using Apache2::Reload on a development machine, but I
can't for the life of me f
I'm currently using Apache2::Reload on a development machine, but I
can't for the life of me figure out what it's doing and why.
I'm coming across weird behavior such as the following just about every
5 minutes:
1. Have a perfectly working page.
2. Change some `print "foo"` to `print "bar"` (
Are the t/apr-ext/*.t tests supposed to fail? No matter how hard to
try I always get this on OpenBSD 3.9 with perl 5.8.8, Apache-2.2.2
and mod_perl-2:
Failed Test Stat Wstat Total Fail Failed List
of Failed
-
I'm compiling Apache-2.2.2 with mod_perl-2 on OpenBSD 3.9 as well as
a with a manually compiled perl-5.8.8. The issues I'm having is at
the mod_perl test suite, these are the results:
~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!
~!~!~!~!~!~!~!~!~!~!~
Failed Test
Follow the steps in the section entitled "Installing mod_perl with
mod_ssl (+openssl)" on http://modperlbook.org/html/ch03_06.html to
the letter and everything should work out smoothly. Also, consider
using Apache 2.2.2 and mod_perl-2 instead. Lastly, buy this book:
http://www.oreilly.com/c
There is a plethora of different ways to handle sessions in perl
driven websites. I'll throw in my 2 cents by describing how I've
always liked to do it. My solution assumes that your using an SQL
database for persistent data storage; but that obviously isn't a
requirement, there are a lot o
This post is in the context of mod_perl-2 handler's such as PerlResponseHandler MyModule::handler().When "use strict" in one of my modules has something to complain about it puts an error message into the vhosts's error log as any good warnings/errors module should, for example /www/addons/logs/er
