Hi,
The problem was that on our machines ( Solaris 2.6,
Apache 1.3.14, Modperl 1.26) we are constantly getting
a child segmentation fault (11) . One mail in the
news group suggested using PERL_USELARGEFILES=0 in
addition to the normal configuration for modperl
installation. We tried that with
John Michael wrote:
Where can I find information on how to install modules like:
Apache::Request libapreq-0.33.tar.gz
Apache::DBIApacheDBI-0.88.tar.gz
Would I install these as regular perl modules or are they installed as
apache modules?
They are regular perl modules.
John Michael wrote:
Checking if your kit is complete.
Looks good
Writing Makefile for libapreq
mkdir blib/lib
mkdir blib/lib/auto
mkdir blib/lib/auto/libapreq
mkdir blib/man3
cp libapreq.pod blib/lib/libapreq.pod
cp lib/Apache/libapreq.pm blib/lib/Apache/libapreq.pm
make[1]: Entering
I have successfully installed mod_perl and am using it.
I have two question.
1- Currently I have designated a /pm directory to contain my mod_perl
codes, a collection of classes. I then have instances of these launched
from non /pm directory. I did this so that I don't have to be back at
I have some state data that I need to persist between requests. At the
moment these are COM objects, but they'll be ported to Perl Classes. It
is quite important that only one of these instances exist per web
server. These instances are too large to write and read to file on every
request. So I
-- Chui G. Tey [EMAIL PROTECTED]
I have some state data that I need to persist between requests. At the
moment these are COM objects, but they'll be ported to Perl Classes. It
is quite important that only one of these instances exist per web
server. These instances are too large to write
Will the different child processes created by Apache share the same
variable? Or will each child create an additional instance?
Each child has a separate interpreter and thus a separate instance of
your global. If you need to co-ordinate data between processes, you
might want to look at
1- Currently I have designated a /pm directory to contain my mod_perl
codes, a collection of classes. I then have instances of these
launched
from non /pm directory. I did this so that I don't have to be back at
cgi-bin perdicament where all my CGIs are in one directory. I never
liked that
dougm 01/11/04 20:50:57
Modified:src/modules/perl modperl_util.c
Log:
check if @DynaLoader::dl_librefs actually has any elements
in modperl_xs_dl_handles_get() before calling apr_array_make()
Revision ChangesPath
1.28 +5 -0
dougm 01/11/04 21:12:33
Modified:src/modules/perl modperl_util.c
Log:
need some parens around AvFILL(librefs) = 0 check
Revision ChangesPath
1.29 +1 -1 modperl-2.0/src/modules/perl/modperl_util.c
Index: modperl_util.c
dougm 01/11/04 21:19:01
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_callback.c modperl_config.c
modperl_config.h modperl_interp.c modperl_types.h
Log:
add a per-request cleanup function that properly deals with PerlInterpScope
11 matches
Mail list logo
