Re: [mp1] callback called exit (many times)

Am I right deducing, that I should attempt recompiling perl with -DEMERGENCY_SBRK? Try to, but this doesn't solve the original problem. You still have to try to narrow down the code that causes the problem. Using ab or a similar load tester might help to stress test. Using tools

Re: default Content-Length calculation has been removed in 2.0 (was Re: mod_perl 2.x vs. mod_perl 1.x benchmarks)

Issac Goldstand wrote: I think I got it... I was under the understanding that each fireman could only hande 1 bucket at a time, but there could be up to as many buckets as firemen on the stack at any given time... Do you know why it's like that? a limitation of the current mpms, there

Re: default Content-Length calculation has been removed in 2.0 (wasRe: mod_perl 2.x vs. mod_perl 1.x benchmarks)

Well, it's been getting *WAY* OT - more geared for dev@httpd if anywhere, but I'm sure they've argued this out already :-) My initial ideas all counted on the fact that each handler/filter would have a way of getting its own per-request thread... On the opposite, IMHO this is very ON topic,

[patch] Apache::DB now works with 5.8.0+

To all those having problems with Apache::DB and perl 5.8.0+ (CC'ing all those who have complained recently). Try this patch: --- Apache-DB-0.06/DB.pm.old 1999-10-12 07:50:33.0 +0800 +++ Apache-DB-0.06/DB.pm 2002-11-29 18:03:47.0 +0800 @@ -14,6 +14,7 @@

Re: [mp 2.0] can not compile mp 1.99_07

Dipl.-Inform. Kai Hofmann wrote: I tried to compile 1.99_07 - but there is a definition of IoTYPE_WRONLY and IoTYPE_REONLY within the file apr_perlio.c which can not be resolved unter SuSE Linux 7.2 with Apache 2.0.43 I greped all includes without any success where these things will be

Thread::Pool problem

A lot of time ago some of you help us and your contribution to our work has been very important. We use the Thread::Pool version 0.22 module in our system and it works very well (under solaris SunOS 5.8 sun4u sparc SUNW,UltraAX-i2). Now we have installed the new version 0.28 of the module under a

Apache doesn't load anymore modules after mod_perl.so

I did a 'strace' through httpd and found that Embperl.so isn't loaded. This probably explains the error in the previous mail. After tinkering around a little, it turns out that the LoadModule directive in Apache's configuration isn't loading any modules after mod_perl.so has been loaded. This

mod_perl configuration for ISP/webhost (disabling mod_perl access for normal users)

i've read the [EMAIL PROTECTED] archive (mainly the security suggestion thread in nov 2000). it seems that quite a few people (including me, recently) want to install mod_perl. usually they need mod_perl because they want to write apache modules in perl instead of c (including me; i really

Fwd: Red Hat's use of mod_perl

Thanks Chip, great info! please keep those coming, we will update the site once we have several of these new additions. The original request is here: http://use.perl.org/articles/02/11/29/1837238.shtml?tid=11 Original Message Subject: Red Hat's use of mod_perl Date: 29 Nov

Re: Apache doesn't load anymore modules after mod_perl.so

Lai Zit Seng wrote: After tinkering around a little, it turns out that the LoadModule directive in Apache's configuration isn't loading any modules after mod_perl.so has been loaded. This is the case with mod_perl-1.99_07 and mod_perl-1.99_06. But with mod_perl-1.99-05, it works (and the