in reply to Cache :: FastMmap

It sounds like you are using a Perl which was built with thread support. You can find this out with:

perl -V | grep archname=

or:

perl -V | grep useithreads=

In the first example, the archname usually indicates if it is a threaded Perl. On my threaded version of 5.10.0, I get:

osname=linux, osvers=3.13.0-24-generic, archname=x86_64-linux-thread-multi

In the second example, you are looking to see if useithreads is set to define. Again, from my threaded 5.10.0 install:

useithreads=define, usemultiplicity=define

Try installing a non-threaded Perl and set Apache to use that instead of the system Perl. How to do that is left as an exercise for the reader, as it is beyond the scope of the question. However, something like Plenv or Perlbrew can make that relatively painless.

Replies are listed 'Best First'.
Re^2: Cache :: FastMmap (mod_perl)
by tye (Sage) on Aug 19, 2015 at 19:06 UTC
    Try installing a non-threaded Perl and set Apache to use that instead of the system Perl.

    The instructions followed (https://github.com/eanders/CUFTS-Install-Notes/blob/master/CUFTS.mediawiki) mention mod_perl. So your suggestion should probably be changed to:

    Try installing a non-threaded Perl and rebuild Apache to use that instead of the system Perl.

    which might even be a major pain when Apache was obtained via "apt-get install ... apache2 ..." along with a ton of other packages, some of which come pre-configured to use the instance of Apache provided by apt-get.

    It sounds like you are using a Perl which was built with thread support.

    As I noted elsewhere, the problem appears to be that Perl threads are actually being created (presumably by Apache). Just having a Perl that supports the creating of threads should not be enough to cause the reported problems (as near as I can tell).

    - tye        

[reply]

In Section Seekers of Perl Wisdom