On Tue, Feb 27, 2007 at 05:19:02PM -0500, Perrin Harkins wrote:
> On 2/23/07, Josef Karthauser <[EMAIL PROTECTED]> wrote:
> >The same think happens with 2.0.2, so I'm guessing that it's probably a
> >misunderstanding on my part on how it works -- can someone please fill
> >me in, or point me to the
Mark Stosberg wrote:
Hello,
Recently I ran into a bug with File::MMagic where it returns
inconsistent results under mod_perl.
Could it simply be a matter of fixing the use of the DATA handle, as
Stats suggest here?
http://mail-archives.apache.org/mod_mbox/perl-modperl/200403.mbox/[EMAIL
PROTE
On 2/23/07, Josef Karthauser <[EMAIL PROTECTED]> wrote:
The same think happens with 2.0.2, so I'm guessing that it's probably a
misunderstanding on my part on how it works -- can someone please fill
me in, or point me to the specific documentation please?
It looks like you were trying to use it
Hi folks,
About once every 15-45 minutes or so a httpd process will segfault when serving
a modperl page. I've built apache httpd, modperl and perl with debuging
symbols, and have gotten a few core images.
Here are the relvent software versions:
FreeBSD 6.1-RELEASE-p14 running an SMP kernel
Per
Hi Mark,
What's interesting is that the same version of File::MMagic works
correctly on a different machine. I suspect that some other module
loaded has changed a global variable that File::MMagic depends on.
Someone has a bug report and patch to that effect here:
http://rt.cpan.org/Public/Bug/
Hello,
Recently I ran into a bug with File::MMagic where it returns
inconsistent results under mod_perl.
I'm interested in getting this bug fixed, or using an alternative module
that works.
What's interesting is that the same version of File::MMagic works
correctly on a different machine. I susp
Ok. I just went through the CPAN code...
at least in Cache::Memcached, no socket connection is made until a
get. in fact, they all seem to be made as needed, and not cached.
in any event, I use this code under MP2 , and do all my get/sets as
MyApp::Functions::Memcached::memcached_
On Feb 27, 2007, at 8:40 AM, Perrin Harkins wrote:
That seems very unlikely to me, unless you are using it in a way that
doesn't cause it to connect before forking. You can't open sockets,
fork and then use the same socket in both processes.
Right now I connect pre-fork in the parent -- it w
>I suggest loading the module in the parent but not opening any
>connections until after the fork.
>
How to write the codes then?Currently I've written it as:
sub handler
{
my $r = shift;
my $q = Apache::Request->new($r);
...
my $memd = new_memcached(); # open the socket to mem
On 2/27/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
It seems to work fine with a single memcached connection for
everything ( instantiated pre-fork ).
That seems very unlikely to me, unless you are using it in a way that
doesn't cause it to connect before forking. You can't open sockets,
f
10 matches
Mail list logo