Hi and welcome indeed.
Maybe one thing first : when posting to the list, do not just hit "reply" on a message
that you received previously. Create a *new* message, with a subject corresponding to what
you are asking. Then later, when someone responds, you can "reply" and keep the subject
ident
Hello List,
I'm sending this message to know if there are some hints/tips to help
with the problem we're facing.
The problem is that for a same query repeated over time,
reply time can be as short as 5ms and as long as 1s.
Since there is neither correlation with CPU load or RAM usage, nor with
On Friday 16 July 2010 14:24:17 Hans de Groot wrote:
> PerlPostReadRequestHandler ModPerl::VHost
>
I think this is too early in the request cycle to do that. Try a
PerlMapToStorageHandler. You may also have a look at Apache2::Translation. The
documentation needs a rewrite, I know. It's purpose
Hello,
I am trying to use the proxypass directive in mod_perl.
I actually got this working (after upgrading to mod_perl 2.4.x) so I
know it is possible to use proxy pass here
but I still have one problem.
I have a perl hander:
#file:ModPerl/VHost.pm
#-
package ModPerl::
> Variable "$x" will not stay shared at /usr/local/prefork/perl/thing.cgi line
> 10.
Yes, I foolishly looked in the per-virtual-host error log, instead of
the global error log
where the warning was placed neatly.
> which, with a quick googling of 'mod_perl variable will not stay shared',
I was b
Erik Aronesty wrote:
Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone
Yes, it's a problem with ModPerl::Registry, I agree. It's not mentioned here:
http://perl.apache.org/docs/2.0/api/ModPerl/Registry.html#Caveats
Where it should be.
Absolutely, i'll patch the do
> Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone
Yes, it's a problem with ModPerl::Registry, I agree. It's not mentioned here:
http://perl.apache.org/docs/2.0/api/ModPerl/Registry.html#Caveats
Where it should be.
> is trying to get an old CGI script to work under m
Michael Peters wrote:
Erik Aronesty wrote:
This can not be called "verbose", because it's rather hard to find, but
it's worth reading.
http://perl.apache.org/docs/general/perl_reference/perl_reference.html#toc_Remedies_for_Inner_Subroutines
But normally perl/mod_perl will warn you in the log
Erik Aronesty wrote:
mod_perl should be *extremely* verbose in pointing this change out to
developers, as
it is *extremely* difficult to diagnose.
Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone is trying to get an old
CGI script to work under mod_perl then they'd
-8<-- Start Bug Report 8<--
1. Problem Description:
It's well known that file-scoped lexicals don't work intuitively in
CGI programs under mod_perl.
When mod_perl calls the same CGI program twice, file-scoped lexicals
are not rebound.
Some people are aware
Hi,
At http://perl.apache.org/docs/2.0/user/config/custom.html#C_SERVER_CREATE_it
should be noted about this function (and also about DIR_CREATE) that
it
will be called if there is at least one custom directive present in
httpd.conf.
So setting so called 'system defaults' is not possible this way
11 matches
Mail list logo
