Apache::SizeLimit has a long-standing bug on Linux where it never actually
kills a child, because of Perl's caching of ppid info internally, and the
way this interacts with Apache's forking.
See this thread for details:
http://mail-archives.apache.org/mod_mbox/perl-modperl/200505.mbox/[EMAIL
Dave Rolsky wrote:
Apache::SizeLimit has a long-standing bug on Linux where it never
actually kills a child, because of Perl's caching of ppid info
internally, and the way this interacts with Apache's forking.
See this thread for details:
Dave Rolsky wrote:
Apache::SizeLimit has a long-standing bug on Linux where it never
actually kills a child, because of Perl's caching of ppid info
internally, and the way this interacts with Apache's forking.
See this thread for details:
On Fri, 16 Jun 2006, Geoffrey Young wrote:
Dave Rolsky wrote:
Apache::SizeLimit has a long-standing bug on Linux where it never
actually kills a child, because of Perl's caching of ppid info
internally, and the way this interacts with Apache's forking.
See this thread for details:
On Fri, 16 Jun 2006, Perrin Harkins wrote:
Dave Rolsky wrote:
Apache::SizeLimit has a long-standing bug on Linux where it never actually
kills a child, because of Perl's caching of ppid info internally, and the
way this interacts with Apache's forking.
See this thread for details:
On Fri, 16 Jun 2006, Dave Rolsky wrote:
But I wasn't saying I'm going to release it, screw you. I was saying I'd
like to release a bug-fixed version, because I have no idea when mod_perl
1.30 will come out, if ever, but I can fix this bug and release
Apache::SizeLimit 0.04 right now.
I
Hi folks,
Is there a way to log a debug-level message without Apache2::Log writing
the filename and line number of the caller? Could I override something
in Apache2::Log?
This behaviour is documented in man Apache2::Log.
I'm using Log4perl, so every debug-level message comes out with
On Friday 16 June 2006 17:23, Perrin Harkins wrote:
Dave Rolsky wrote:
Apache::SizeLimit has a long-standing bug on Linux where it never
actually kills a child, because of Perl's caching of ppid info
internally, and the way this interacts with Apache's forking.
See this thread for
On Fri, 16 Jun 2006, Torsten Foertsch wrote:
Yes, since 5.8.1. The problem is that the now old linux-threads implementation
returns different values for getpid() and getppid() for different threads.
Hence Perl decides better to cache these values and update the cache on
fork() to make it more
Are there any objections to me doing this?
uh, yeah. how about you submit the patch here and we incorporate it?
just uploading modules to CPAN that collide with the namespace of
existing modules that are part of a distrubution isn't the way things
typically work. I mean, you wouldn't ask
supported in a single release if Apache::SizeLimit does have a new,
separate life on CPAN...
I'm not sure thats easily possibly with one module because its Apache::SizeLimit
AND Apache2::SizeLimit.
If you put Apache::SizeLimit on CPAN which supported both, we'd probably have
to remove the one
On Fri, 16 Jun 2006, Geoffrey Young wrote:
But I wasn't saying I'm going to release it, screw you.
sure sounded that way, but ok.
I apologize. Note the question mark in the title of this thread. I thought
I was offering to help the mod_perl project, honestly.
I was saying I'd like to
Philip M. Gollucci wrote:
supported in a single release if Apache::SizeLimit does have a new,
separate life on CPAN...
I'm not sure thats easily possibly with one module because its
Apache::SizeLimit
AND Apache2::SizeLimit.
so. it's just a namespace - Apache2::SizeLimit could simply be a
I apologize. Note the question mark in the title of this thread. I
thought I was offering to help the mod_perl project, honestly.
my last comment was meant to be an understanding as well, but it didn't
come off that way. sorry. if we didn't know eachother in person then I
might have spent
Geoffrey Young wrote:
let's just get them working together in the same distribution, put in on
cpan, and pull it into each mod_perl release as they happen...
+1 here.
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
I'm compiling Apache-2.2.2 with mod_perl-2 on OpenBSD 3.9 as well as
a with a manually compiled perl-5.8.8. The issues I'm having is at
the mod_perl test suite, these are the results:
~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!
~!~!~!~!~!~!~!~!~!~!~
Failed Test
this is a longshot...
i need to generate rsa pairs in my mod-perl app
i tried the cpan modules, and they're all slowslowslow
so then i thought 'ok, i'll just pipe to openssl'. that works.
but then i'm out the door just now to get a drink and play some buck
hunt and i think-
17 matches
Mail list logo
