Josh Bernstein wrote:
> Hey All,
>
>I'm getting this error when I try to make mod_perl2, under solaris 9
...
> Any one have any ideas? Oh and I'm running Solaris 9, with Apache
> 2.0.40cvs, it should also be noted that the mod_perl was pulled from CVS
> on July 8th. Is this just a broken bu
Eric L. Brine wrote:
> Is there any easy way to check which options were used to compile mod_perl.
> Or more specifically, is there an easy way to check which type handlers a
> mod_perl build allows, if it allows stacked handlers, if it allows method
> handlers and if it allows perl sections? Than
Is there any easy way to check which options were used to compile mod_perl.
Or more specifically, is there an easy way to check which type handlers a
mod_perl build allows, if it allows stacked handlers, if it allows method
handlers and if it allows perl sections? Thanks.
--
Eric L. Brine
[EMAIL
I went through this recently
set $apr = Apache::Registry->instance($r) rather than ->new($r);
> -Original Message-
> From: Tim Sebastian Böckers [mailto:[EMAIL PROTECTED]]
> Sent: 28 June 2002 18:44
> To: [EMAIL PROTECTED]
> Subject: param trouble
>
>
> dear list,
>
> i run into som
> Changing a line in CGI::Carp
> < sub ineval { $^S || _longmess() =~ /eval [\{\']/m }
> ---
> > sub ineval { _longmess() =~ /eval [\{\']/m }
> Are there any solutions to this problem that don't involve changing
> CGI::Carp? Perhaps I should just rip the code that I want out of CGI::Carp?
Why n
Hey All,
I'm getting this error when I try to make mod_perl2, under solaris 9
>make
cd "src/modules/perl" && make -f Makefile.modperl
make[1]: Entering directory `/usr/share/src/modperl-2.0/src/modules/perl'
gcc -I/usr/share/src/modperl-2.0/src/modules/perl
-I/usr/share/src/modperl-2.0/xs
Internet Software Engineer (PERL)
About Web Services is seeking an Internet Software Engineer to maintain and
develop new applications for it's hosting platform. About Web Services is a
division of About.com that provides hosting solutions to more than 4 million
web sites including freeservers.c
On Wed, 10 Jul 2002, Matt Sergeant wrote:
> Ah, in that case I'm recommending Dave's stuff. It's more flexible and
> doesn't use that irritating -param stuff. Though I have to do a little
> more research to be certain some things are possible (like turning on
> stack traces globally).
Actually,
On Wed, 10 Jul 2002, Perrin Harkins wrote:
> Matt Sergeant wrote:
> > On Wed, 10 Jul 2002, Fran Fabrizio wrote:
> >>Just to confirm, the end result of Matt's slide presentation was that
> >>Error.pm was good, and you should use it, but you should not use the
> >>try/catch syntax, or at the bare m
Perrin Harkins wrote:
> Stas Bekman wrote:
>
>> I think the idea was to have a special thread running whose only purpose
>> is monitoring the pool of idle interpreters.
>
>
> That sounds like a better solution.
The drawback is that there will be two different solutions for threaded
and prefor
Stas Bekman wrote:
> I think the idea was to have a special thread running whose only purpose
> is monitoring the pool of idle interpreters.
That sounds like a better solution.
> I believe that we can add a Perl space hook that sets a flag that
> condemns an interpreter to death.
The other prob
Andy Lester wrote:
>>
>> my $test="hans";
>>
>>
>
> Don't you also need
>
> PerlModule Apache::PerlSections
>
> Maybe?
that shouldn't be required. my guess is that EVERYTHING=1 was not
specified in the upgrade build procedure.
check /perl-status?hooks and make sure that PerlSections
Perrin Harkins wrote:
> Stas Bekman wrote:
>
>> If you are talking about threaded mpms, we will need to develop new
>> tools to restrict the size of the perl interpreters in the pool.
>
>
> I was thinking about that too. Are there hooks for causing an
> interpreter to exit? Is it safe t
I think I made a mistake posting this query over the holiday weekend, so I'm
gonna speak up again.
I have a couple of strange bugs showing up in Bricolage that have something
to do with Apache->print timing out (with Win 95 and Mac OS 9 -- yes, these
folks need to join the new millennium), and ha
>
> my $test="hans";
>
Don't you also need
PerlModule Apache::PerlSections
Maybe?
xoxo,
Andy
--
'Andy Lester[EMAIL PROTECTED]
Programmer/author petdance.com
Daddy parsley.org/quinn Jk'=~/.+/s;print((split//,$&)
[unpack'C*',"n2]3%+>
just upgraded from 1.3.22/mod_perl 1.26 to 1.3.26/1.27 and while all
the other stuff is working fine my daemon does not recognize the
-directive anymore !?
test in httpsd.conf:
my $test="hans";
# /usr/local/apache/bin/httpsdctl start
Syntax error on line 105 of /usr/local/apache/conf/httpd.
Stas Bekman wrote:
> If you are talking about threaded mpms, we will need to develop new
> tools to restrict the size of the perl interpreters in the pool.
I was thinking about that too. Are there hooks for causing an
interpreter to exit? Is it safe to simply call CORE::exit? I'd like to
ma
Kent, Mr. John wrote:
> Greetings,
>
> Have noticed that modperl-2.0 servers running on Solaris 2.7 start
> off at 23M in size. Five hours later they were at 38M. If allowed to
> continue
> they could eventually use up all available RAM and crash the system.
>
> Stopping then restarting retur
Matt Sergeant wrote:
> On Wed, 10 Jul 2002, Fran Fabrizio wrote:
>>Just to confirm, the end result of Matt's slide presentation was that
>>Error.pm was good, and you should use it, but you should not use the
>>try/catch syntax, or at the bare minimum only catch in your outermost
>>handler. Is tha
use CGI::Carp qw(fatalsToBrowser); was having no effect on my modules.
Changing a line in CGI::Carp
< sub ineval { $^S || _longmess() =~ /eval [\{\']/m }
---
> sub ineval { _longmess() =~ /eval [\{\']/m }
,by advise from a mail I found in archives from last year, produced the
results that I was
[resent to modperl list; earlier copy mistakenly cc'd to "p5p"]
Does anyone know what's causing the Apache::Request object to
leak here? See # XXX comment below:
package Apache::test;
sub Apache::Request::DESTROY{warn "DEAD: $_[0]\n"}
sub Apache::DESTROY{warn "Dead: $_[0]\n"}
Does anyone know what's causing the Apache::Request object to
leak here? See # XXX comment below:
package Apache::test;
sub Apache::Request::DESTROY{warn "DEAD: $_[0]\n"}
sub Apache::DESTROY{warn "Dead: $_[0]\n"}
use Devel::Peek;
use Apache::Request;
sub handle
Joe Schaefer wrote:
>>Somehow the assignment operator MUST be involved in the leak here.
>>(You only get a leak when the *same* reference (*SV) is on both sides
>>of the assignment).
>
>
> Could someone with modperl 1.2x built using a perl 5.8 release candidate
> please test this out:
I got t
On Wed, 10 Jul 2002, Fran Fabrizio wrote:
>
> Just to confirm, the end result of Matt's slide presentation was that
> Error.pm was good, and you should use it, but you should not use the
> try/catch syntax, or at the bare minimum only catch in your outermost
> handler. Is that correct? We were
Just to confirm, the end result of Matt's slide presentation was that
Error.pm was good, and you should use it, but you should not use the
try/catch syntax, or at the bare minimum only catch in your outermost
handler. Is that correct? We were debating this just yesterday in our
office.
-Fr
Joe Schaefer <[EMAIL PROTECTED]> writes:
[...]
> Somehow the assignment operator MUST be involved in the leak here.
> (You only get a leak when the *same* reference (*SV) is on both sides
> of the assignment).
Could someone with modperl 1.2x built using a perl 5.8 release candidate
please tes
26 matches
Mail list logo
