e-mol Development Team wrote:
After some thinking time I decided to compile perl 5.8.0 on the older system
that did have 5.6.1. It would seem it has nothing to do with perl 5.8.0. I
compiled perl 5.8.0 on the older system and preloading worked just like it should.
Now I know that it does not have
After some thinking time I decided to compile perl 5.8.0 on the older system
that did have 5.6.1. It would seem it has nothing to do with perl 5.8.0. I
compiled perl 5.8.0 on the older system and preloading worked just like it should.
Now I know that it does not have anything to do with perl or
I think next I may try and see if perl 5.6.1 can be build on the 5.8.0 system
and see what this leads to.
I wonder if it could be the newer gcc or glibc?
This is quite possible, since the sharing mostly comes from your OS, not
specificly from Perl.
You may also want to try the latest perl-5.8.1
>e-mol Development Team wrote:
>>>diff -u 5.6.1.txt 5.8.0.txt
>
>The two builds are quite different, I have pointed out below at least a few
>major differences.
>
>> [EMAIL PROTECTED] src]# diff -u 5.6.1.txt 5.8.0.txt
>> --- 5.6.1.txt 2003-09-03 14:07:02.0 -0400
>> +++ 5.8.0.txt 2003-09
[make sure to keep the replies on the list. Thank you!]
e-mol Development Team wrote:
diff -u 5.6.1.txt 5.8.0.txt
The two builds are quite different, I have pointed out below at least a few
major differences.
[EMAIL PROTECTED] src]# diff -u 5.6.1.txt 5.8.0.txt
--- 5.6.1.txt 2003-09-03 14:07:02
e-mol Development Team wrote:
I have two servers running Apache 1.3.27 and mod_perl 1.27 both severs are
running identical httpd.conf and startup.pl configurations. One is running
Perl 5.8.0 the other is running 5.6.1. When I do the preloading of modules on
the 5.6.1 system all seems well and sha
I have two servers running Apache 1.3.27 and mod_perl 1.27 both severs are
running identical httpd.conf and startup.pl configurations. One is running
Perl 5.8.0 the other is running 5.6.1. When I do the preloading of modules on
the 5.6.1 system all seems well and shared memory goes up while unsha
What is the most effecient way of preloading modules to use for mod_perl? I
currently use a startup.pl within my httpd.conf, but I know I will not have
access to this configuration file on my shared hosting account.
Scott Anderson
BTS/Payright
[EMAIL PROTECTED]
206-242-7088 xt231
> * initialize everything in the parent Apache, just make sure to create
> new DBI connections in the children.
That's what I would do. It increases the amount of shared memory.
Disconnect the DBI connection when you're done with it. Apache::DBI
doesn't cache connections during startup, so th
Hi,
I have some modules that use the idiom
package Foo;
use Bar;
{
my $bar = Bar->new(args);
sub bar { return $bar }
}
which works fine until one tries to preload them in startup.pl.
I realized that, by preloading, I was innocently sharing the same DBI
object between Apache children (not
"Eric Jain" <[EMAIL PROTECTED]> writes:
> Any Perl module required from within a module which has been preloaded
> through PerlRequire or PerlModule in httpd.conf will be preloaded into
> shared memory as well. Correct?
Yes. Thus saving some latency when Apache forks a new child.
--
Dave Hodg
Any Perl module required from within a module which has been preloaded
through PerlRequire or PerlModule in httpd.conf will be preloaded into
shared memory as well. Correct?
--
Eric Jain
Okay, I have finally tracked down the source of the problem I am having and
would appreciate your suggestions and work-arounds.
First, I am using mod_perl; however, like the docs say, I wanted to preload
modules, so, I have in my httpd.conf:
PerlRequire /startup.pl
For a startup.pl I have:
use
13 matches
Mail list logo
