On Wed, Sep 22, 2004 at 10:17:34PM -0400, Stas Bekman wrote:
> Joe, as 2.0.52 is about to be released. Can that fix for NetBSD applied to
> the 0.9 trunch (and head) if it does the trick? Thanks.
It's been in both branches for a while so hopefully it will get picked
up, yep.
joe
--
Report prob
[EMAIL PROTECTED] wrote:
Greetings,
The problem is that the script takes more than 3 or 4 seconds to execute
sometimes.
So we have a script that takes 3-4 seconds to execute, each varaiable is
defined with my $var. and when the script ends it resets the value of the
variables using undef.
If multip
Tom Schindl wrote:
[EMAIL PROTECTED] wrote:
Greetings,
The problem is that the script takes more than 3 or 4 seconds to execute
sometimes.
So we have a script that takes 3-4 seconds to execute, each varaiable is
defined with my $var. and when the script ends it resets the value of the
variables usi
This isn't a show-stopper for me, but I thought I'd post it in case it is
a real problem. I'll be happy to do whatever testing is necessary...
I'm running a fully updated Fedora Core 2, but I've compiled Perl, Apache,
and mod_perl myself.
Thanks! - Scott
-8<-- Start Bug Rep
-8<-- Start Bug Report 8<--
1. Problem Description:
I'm also suffering from the common
/usr/bin/ld: cannot find -lapr-0
problem. Copying /usr/local/apache2/lib/libapr-0.a to /usr/lib
make the link problem go away but I still see many
"undefine
-8<-- Start Bug Report 8<--
1. Problem Description:
On a plain boring box running debian stable, the simplest build of
apache 2.0.51 with a static linked mod_perl 1.99.16 segfaults
immediately on start. I've been running round in circles on this all
eve
Matthew Hodgson wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
On a plain boring box running debian stable, the simplest build of
apache 2.0.51 with a static linked mod_perl 1.99.16 segfaults
immediately on start. I've been running round in c
Jon Forrest wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
I'm also suffering from the common
/usr/bin/ld: cannot find -lapr-0
problem. Copying /usr/local/apache2/lib/libapr-0.a to /usr/lib
make the link problem go away but I still see m
[EMAIL PROTECTED] wrote:
This isn't a show-stopper for me, but I thought I'd post it in case it is
a real problem. I'll be happy to do whatever testing is necessary...
I'm running a fully updated Fedora Core 2, but I've compiled Perl, Apache,
and mod_perl myself.
Thanks! - Scott
-8<---
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard on
improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
-8<-- Start Bug Report 8<--
Matthew Hodgson wrote:
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard on
improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
-8<-- Start Bug Report
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard on
improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
Okay, my previous build using latest mod_perl cvs was slightly scre
Hi all -
> You use interpreter pool size control directives:
> http://perl.apache.org/docs/2.0/user/config/config.html#Threads_Mode_Specific_Directives
>
>
> You don't need to prevent anything. It's just that if your server uses
> very little modperl and mostly doing static requests, you can have
Larry Leszczynski <[EMAIL PROTECTED]> writes:
[...]
> The above link mentions the memory benefits of having few perl intepreters
> among many threads e.g. if you have a mix of static and dynamic content.
> But it made me wonder what is the effect regarding the "spoonfeeding slow
> clients" scenar
Larry Leszczynski wrote:
Hi all -
You use interpreter pool size control directives:
http://perl.apache.org/docs/2.0/user/config/config.html#Threads_Mode_Specific_Directives
You don't need to prevent anything. It's just that if your server uses
very little modperl and mostly doing static requests,
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> It depends on many things. For example it's possible to have a simple filter
> written in C, which will accept all the data from the response handler
> and then spoonfeed the client, just like the proxy does.
Stas, related question: I was looking o
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
It depends on many things. For example it's possible to have a simple filter
written in C, which will accept all the data from the response handler
and then spoonfeed the client, just like the proxy does.
Stas, related question: I
Clayton Cottingham wrote:
Its true, but on a secured intranet it shouldn't be so bad
For me there's no ``shouldn't be so bad''. I only stick with something
that is known as good (secure), nothing else. But that's _my_ oppinion
about security (and no customer/user complained yet).
When the PHB {p
18 matches
Mail list logo
