Hi all,
I'm having a hard time getting mod_perl2 to make tests automatically as
part of an install script. What happens has happened many times before,
but was not a problem since we knew the workaround.
The problem is that the first time make test is made, the system times
out waiting for
Jens Petter Salvesen wrote:
The system in this case is RHEL 5 64bit, but we experience the same
hiccup on RHEL 4 32bit as well.
Anybody have a clue about why this is happening?
I've seen this happen when the tests tried to load an httpd module that
wasn't in the build, but this could be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snippet]
5.6.x in the wild
~ A recent change to the GNU coreutils package has broken the
~ Configure script for 5.6.x (or rather, it's been fixed for more recent
~ perls for ages, but hasn't been, and is unlikely to be backported to
~ 5.6.x).
On May 11, 2008, at 2:52 AM, Marc Lambrichs wrote:
Here's my view: they create a parent App::Handler and in every
virtual host they create a Site::Handler which has App::Handler as
base. My first guess is that under mod_perl you don't know which
Site::Handler will be called. Ofcourse, at
Hi,
we have mod_perl auth handler
if the form(html) sumission is GET the sumitted data is avaible insid the
mod_perl auth handler and also after that.
But strange this is if the form submission is Post the data is available
with the mod_perl handler but not after that, After the
execution of
