On Tue, 2006-09-05 at 17:50 -0400, Jonathan Vanasco wrote:
> > Incidentally, I don't see why your Python job queue can't just
> > execute a Perl script to do this job.
>
> didn't really think of that :)
>
> although if i did that, i'd have to do some crazy PID watching thing,
> to make sure I
On Sep 5, 2006, at 4:14 PM, Perrin Harkins wrote:
The memory would be shared by CoW and I haven't seen that zombie
problem.
yeah, but apache instances seem to take up 5-10mb of memory per-
instance. i think 3 is for apache itself, and the rest is various
stuff. 10 requests to this page w
Why wasn't (hasn't) a version 2.0.3 been pushed out that just fixes
problem with the tests? I only found out about this problem about 3
weeks ago, after going through the same banging of the head that so many
other people seem to have. This problem has existed for months and
seems like it could h
On Mon, 2006-09-04 at 13:26 +0200, Andreas Schuldei wrote:
> I would like to generate statistics on what functions in my
> codebase are heavily used, used, barely used or unused.
See Apache::DProf and Devel::Cover.
- Perrin
On Mon, 2006-09-04 at 18:55 -0400, Jonathan wrote:
> fork() within mod_perl
> Probable No.
> online docs suggest this will fork apache+modperl,
> which would
> take up too much memory
> child processes will persist as zombies when c
andy law (RI) wrote:
> I've just finished beating my head against the modperl tests. I
> understand that I'm not alone in having been down this route.
No sir, you are not.
Yes, both status. and content_length_header.t are fixed in SVN and will be
fixed in the 2.0.3 release.
> I also understand
On Mon, 4 Sep 2006 13:26:57 +0200
Andreas Schuldei <[EMAIL PROTECTED]> wrote:
> hі!
>
> I would like to generate statistics on what functions in my
> codebase are heavily used, used, barely used or unused.
>
> I was told that it should be trivial to insert a callback
> function into one of the m
Bas Schulte wrote:
> Hi,
>
> I sort of hoped I could simply get it directly from the Apache request
> object but apparently, I can't.
of course you can? if Apache knows it at all you can get to it from
mod_perl :)
see recipe 5.3 in the mod_perl developer's cookbook for the full
explanation of
I've just finished beating my head against the modperl tests. I
understand that I'm not alone in having been down this route.
I also understand from trawling through the mailing list archives - a
not entirely pain-free procedure itself - that the mod_perl 'grown-ups'
are "getting tired" of answeri
On 9/5/06, Beheer <[EMAIL PROTECTED]> wrote:
We have an modperl2 (1.999.21) application that sometimes gives an
segmentation fault.
I'm having problems with getting Carp:Confess to work. When apache2
gives an segmentation fault, it only prints one line in the error log,
without the information w
Hello,
We have an modperl2 (1.999.21) application that sometimes gives an
segmentation fault.
I'm having problems with getting Carp:Confess to work. When apache2
gives an segmentation fault, it only prints one line in the error log,
without the information where the segmentation fault originates
Hi Philip,
Just a note to thank you for taking the time to put together an example.
It's very much appreciated, and has taught me a fair bit. Your comments,
examples and suggestions have enabled me to create a working prototype.
I have a few long evenings with the Mod_perl docs I believe! :)
R
12 matches
Mail list logo