Stas Bekman wrote:
Pratik wrote:
Looks like this patch is solving all the problems :)
Thanks Pratik, I'll wait till monday before I commit it, in case someone
has an input. And then we can get a new RC out.
In fact I said it wrong. I wanted to get it out after RC3 is released so
we can test bett
mod_perl 1.99_20 (2.0.0-RC3) is out:
http://perl.apache.org/dist/mod_perl-2.0.0-RC3.tar.gz
http://perl.apache.org/dist/mod_perl-2.0.0-RC3.tar.gz.asc (gpg sig)
CPAN:
file: $CPAN/authors/id/G/GO/GOZER/mod_perl-2.0.0-RC3.tar.gz
size: 1416964 bytes
md5: 395897082d4e026effcf0160838989e2
sha
The uploaded file
Apache-Test-1.19.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GO/GOZER/Apache-Test-1.19.tar.gz
size: 142015 bytes
md5: 795c1fcefd0f21b126f573fc46427139
Changes since 1.18:
Test for module.c instead of module.so for IfModule in
find_and_load_module [Chia-Liang
Eric Cholet wrote:
Le 5 janv. 05, à 18:54, Stas Bekman a écrit :
That probably means that Apache installs its own sighandler or
something like that? It certainly shows that a user can't use perl's
ALRM on MaxOSX.
Please post a skip patch?
Sure, but maybe this is also dependent on the version of
Le 5 janv. 05, à 18:54, Stas Bekman a écrit :
That probably means that Apache installs its own sighandler or
something like that? It certainly shows that a user can't use perl's
ALRM on MaxOSX.
Please post a skip patch?
Sure, but maybe this is also dependent on the version of Perl I'm
running,
Perrin Harkins wrote:
On Wed, 2005-01-05 at 11:07 -0500, Stas Bekman wrote:
that's misleading. The platform is supported. I see nothing wrong with
having different error messages.
I was just thinking of making it easier to test, but you're right, it's
not as clear a message.
How about just:
cr
On Wed, 2005-01-05 at 11:07 -0500, Stas Bekman wrote:
> that's misleading. The platform is supported. I see nothing wrong with
> having different error messages.
I was just thinking of making it easier to test, but you're right, it's
not as clear a message.
> How about just:
>
>croak "Unsup
Gisle Aas wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
How do I check the limit for pthread_key_create on linux?
On my Gentoo box I find the limit here:
$ grep PTHREAD_KEYS_MAX /usr/include/bits/local_lim.h
#define PTHREAD_KEYS_MAX1024
Is there a way to check that dynamically
Gisle Aas wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Gisle, could you please provide us some more details about the crash?
I don't really know much more. I have not tried to reproduce this
problem myself with mod_perl and I don't even know exactly which
version of httpd and mod_perl was in u
Eric Cholet wrote:
Le 5 janv. 05, à 17:50, Stas Bekman a écrit :
Eric Cholet wrote:
Le 5 janv. 05, à 17:41, Eric Cholet a écrit :
Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
As I've followed up, you didn't miss anything. As I'm not on your
platform all I can suggest is to dig into the code, i.e.
Le 5 janv. 05, à 17:50, Stas Bekman a écrit :
Eric Cholet wrote:
Le 5 janv. 05, à 17:41, Eric Cholet a écrit :
Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
As I've followed up, you didn't miss anything. As I'm not on your
platform all I can suggest is to dig into the code, i.e.
t/response/TestPer
[EMAIL PROTECTED] wrote:
> Author: geoff
> Date: Wed Jan 5 09:27:46 2005
> New Revision: 124229
>
> URL: http://svn.apache.org/viewcvs?view=rev&rev=124229
> Log:
> a simple checklist for outstanding mp2 todo items
feel free to add or subtract from this as you please, but I thought it was a
goo
The mod_perl project has reached an important and exciting point in its
development cycle - the pending release of mod_perl 2.0, the first official
release of mod_perl designed specifically for Apache 2.0. Critical to the
success of this next generation of mod_perl is that it meets the needs of
t
Gisle, could you please provide us some more details about the crash? I'd
like to write a test for it. I suppose you had it with mp2 worker mpm?
Care to post the output of t/REPORT (in the mp2 source) or mp2bug? Thanks
a lot!
Thank you.
Original Message
Subject: [PATCH] libper
Eric Cholet wrote:
Le 5 janv. 05, à 17:41, Eric Cholet a écrit :
Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
As I've followed up, you didn't miss anything. As I'm not on your
platform all I can suggest is to dig into the code, i.e.
t/response/TestPerl/signals.pm
Thanks, here's what I am seeing
Le 5 janv. 05, à 17:41, Eric Cholet a écrit :
Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
As I've followed up, you didn't miss anything. As I'm not on your
platform all I can suggest is to dig into the code, i.e.
t/response/TestPerl/signals.pm
Thanks, here's what I am seeing in that code:
if
Le 5 janv. 05, à 17:20, Stas Bekman a écrit :
As I've followed up, you didn't miss anything. As I'm not on your
platform all I can suggest is to dig into the code, i.e.
t/response/TestPerl/signals.pm
Thanks, here's what I am seeing in that code:
if (!$static) {
local $ENV{PERL_SIGNALS}
Eric Cholet wrote:
Le 5 janv. 05, à 16:57, Stas Bekman a écrit :
Eric Cholet wrote:
1. Problem Description:
t/perl/signals1..2
# Running under perl version 5.008001 for darwin
# Current time local: Wed Jan 5 16:33:45 2005
# Current time GMT: Wed Jan 5 15:33:45 2005
# Using Test.pm version 1
Eric Cholet wrote:
Le 5 janv. 05, à 16:37, Stas Bekman a écrit :
t/modules/apache_resource...skipped
all skipped: cannot find module 'BSD::Resource'
ah, right, now I understand why I thought we were already testing for it.
Is the above related to Apache::SizeLimit? In any case
On Wed, 2005-01-05 at 17:01 +0100, Eric Cholet wrote:
> From the other
> posts on this thread I understand that this it is not practical or
> feasible to detect this at compile time.
It could be done, but SizeLimit is not required for mod_perl to work,
and mod_perl supports platforms that SizeLi
Perrin Harkins wrote:
On Wed, 2005-01-05 at 10:43 -0500, Stas Bekman wrote:
Perrin Harkins wrote:
I can standardize these messages if it will help.
What do you mean? Patch?
Index: SizeLimit.pm
===
--- SizeLimit.pm (revision 124221)
++
Le 5 janv. 05, à 16:57, Stas Bekman a écrit :
Eric Cholet wrote:
1. Problem Description:
t/perl/signals1..2
# Running under perl version 5.008001 for darwin
# Current time local: Wed Jan 5 16:33:45 2005
# Current time GMT: Wed Jan 5 15:33:45 2005
# Using Test.pm version 1.24
# Using Apache/
Le 5 janv. 05, à 16:37, Stas Bekman a écrit :
t/modules/apache_resource...skipped
all skipped: cannot find module 'BSD::Resource'
ah, right, now I understand why I thought we were already testing for
it.
Is the above related to Apache::SizeLimit? In any case it'd be nicer
if
Stas Bekman wrote:
Eric Cholet wrote:
1. Problem Description:
t/perl/signals1..2
# Running under perl version 5.008001 for darwin
# Current time local: Wed Jan 5 16:33:45 2005
# Current time GMT: Wed Jan 5 15:33:45 2005
# Using Test.pm version 1.24
# Using Apache/Test.pm version 1.19
FAILED
Eric Cholet wrote:
1. Problem Description:
t/perl/signals1..2
# Running under perl version 5.008001 for darwin
# Current time local: Wed Jan 5 16:33:45 2005
# Current time GMT: Wed Jan 5 15:33:45 2005
# Using Test.pm version 1.24
# Using Apache/Test.pm version 1.19
FAILED before any test ou
On Wed, 2005-01-05 at 10:43 -0500, Stas Bekman wrote:
> Perrin Harkins wrote:
> > I can standardize these messages if it will help.
>
> What do you mean? Patch?
Index: SizeLimit.pm
===
--- SizeLimit.pm(revision 124221)
+++ Si
1. Problem Description:
t/perl/signals1..2
# Running under perl version 5.008001 for darwin
# Current time local: Wed Jan 5 16:33:45 2005
# Current time GMT: Wed Jan 5 15:33:45 2005
# Using Test.pm version 1.24
# Using Apache/Test.pm version 1.19
FAILED before any test output arrived
Failed
Perrin Harkins wrote:
On Wed, 2005-01-05 at 09:56 -0500, Stas Bekman wrote:
Ay, for some reason I thought that this was tested for. Pleaes try this patch:
Index: t/conf/post_config_startup.pl
===
--- t/conf/post_config_startup.pl
On Wed, 2005-01-05 at 09:56 -0500, Stas Bekman wrote:
> Ay, for some reason I thought that this was tested for. Pleaes try this patch:
>
> Index: t/conf/post_config_startup.pl
> ===
> --- t/conf/post_config_startup.pl (revision
Eric Cholet wrote:
Le 5 janv. 05, à 15:56, Stas Bekman a écrit :
Eric Cholet wrote:
Hi,
Fresh svn checkout of mp2 / apache 2.0 on MacOSX 10.3.
'make test' fails to start the server. t/logs/error_log reveals that
Apache::SizeLimit
wants BSD::Resource which wasn't installed on my system.
} elsif
Le 5 janv. 05, à 15:56, Stas Bekman a écrit :
Eric Cholet wrote:
Hi,
Fresh svn checkout of mp2 / apache 2.0 on MacOSX 10.3.
'make test' fails to start the server. t/logs/error_log reveals that
Apache::SizeLimit
wants BSD::Resource which wasn't installed on my system.
} elsif (BSD_LIKE) {
On Wed, 2005-01-05 at 15:49 +0100, Eric Cholet wrote:
> Perhaps it would be nicer if this could be detected earlier
It can't be detected earlier in SizeLimit -- it already happens in a
BEGIN block. The server should simply report a warning for SizeLimit
and continue though.
- Perrin
--
On Jan 5, 2005, at 9:49 AM, Eric Cholet wrote:
Perhaps it would be nicer if this could be detected earlier,
unfortunately I'm
still way too clueless to provide a patch.
I never noticed this since I always load BSD::Resource when I set up a
perl installation :-)
Vivek Khera, Ph.D.
+1-301-869-444
Eric Cholet wrote:
Hi,
Fresh svn checkout of mp2 / apache 2.0 on MacOSX 10.3.
'make test' fails to start the server. t/logs/error_log reveals that
Apache::SizeLimit
wants BSD::Resource which wasn't installed on my system.
} elsif (BSD_LIKE) {
# will getrusage work on all BSDs? I shou
Hi,
Fresh svn checkout of mp2 / apache 2.0 on MacOSX 10.3.
'make test' fails to start the server. t/logs/error_log reveals that
Apache::SizeLimit
wants BSD::Resource which wasn't installed on my system.
} elsif (BSD_LIKE) {
# will getrusage work on all BSDs? I should hope so.
35 matches
Mail list logo
