What would happen if you extended the time out period of the server?
Jay Scherrer
On Wednesday 22 December 2004 03:04 pm, Kurt Newman wrote:
> I've recently converted from Apache 1.3.x to Apache 2.0/mod_perl
> 1.99 on RedHat 9.
>
> The issue I'm having are for those applications that attempt to
Kurt Newman wrote:
I've recently converted from Apache 1.3.x to Apache 2.0/mod_perl 1.99 on
RedHat 9.
Kurt, there is no mp1.99. There is 1.99_xx. that xx has a very big
significance, since many problems were fixed between 1.99_01 and 1.99_18.
1) Please upgrade to the latest mp2 version, which is:
Barksdale, Ray wrote:
I agree it should be much smaller. From your reply I seem to have given
the impression I was running on something other than Linux. Sorry about
that. We run Redhat's Fedora Core 2 Linux on x86 (32-bit) for prod/testing.
This was our first try at 64-bit (Redhat Fedora Core 2 AM
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 22, 2004 4:23 PM
> To: Barksdale, Ray
> Cc: modperl@perl.apache.org
> Subject: Re: compile problems
>
> something is very wrong then. On linux I get:
>
> Apache w/o modperl
> stas 8315
I've recently converted from Apache 1.3.x to Apache 2.0/mod_perl 1.99 on
RedHat 9.
The issue I'm having are for those applications that attempt to POST
data (e.g. from a form) that are, for the most part, pretty large (e.g.
46kB). Unfortunately, with this newer version, the applications aren't
re
Barksdale, Ray wrote:
1 thru 6: without mod_perl
7 thru 12: with mod_perl.
Kinda takes you're breath (and ram) away.
1 8738 root 17.1M 15.9M 17.1M 2.0M S httpd
2 8739 nobody 17.1M 15.9M 17.1M 2.0M S httpd
3 8740 nobody 17.1M 15.9M 17.1M 2.0M
1 thru 6: without mod_perl
7 thru 12: with mod_perl.
Kinda takes you're breath (and ram) away.
1 8738 root 17.1M 15.9M 17.1M 2.0M S httpd
2 8739 nobody 17.1M 15.9M 17.1M 2.0M S httpd
3 8740 nobody 17.1M 15.9M 17.1M 2.0M S httpd
4
Barksdale, Ray wrote:
Total: 608169K ( 580M) size, 145465K ( 139M) approx
real size (-shared)
wow, that's a lot. Which mpm is that? Must be worker. And if
you don't
load any modules?
Prefork. That's what you would think :\
PID Size Share VSize Rss M Elapsed LastReq Srvd Client
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 22, 2004 2:28 PM
> To: Barksdale, Ray
> Cc: Matthew Berk; modperl@perl.apache.org
> Subject: Re: compile problems
>
> > Total: 608169K ( 580M) size, 145465K ( 139M) approx
> real size (-
Barksdale, Ray wrote:
Hmm, I managed to get it to work with either -fpic or -fPIC after switching
to shared perl.
Also built with -m64.
I noticed Apache (at least 2.0.52) configures/compiles for -fPIC
automagically.
But once it loads, it is BIG.
(note lotta Apache modules, Apache::Requ
Stas Bekman wrote:
Also it's possible that using Apache::DBI is the better solution, but it
depends on your demands.
doh! please ignore me, instead listen to Perrin. Obviously I've missed the
big letters saying that you already use Apache::DBI.
--
On Tue, 21 Dec 2004, Stas Bekman wrote:
> Randy Kobes wrote:
> > On Tue, 21 Dec 2004, Geoffrey Young wrote:
> >
> >
> >>>-verbose=0 APXS (/usr/local/apache/bin/apxs) query for SBINDIR failed
> >>>APXS (/usr/local/apache/bin/apxs) query for TARGET failed APXS
> >>>(/usr/local/apache/bin/apxs) query
On Tue, 2004-12-21 at 09:26 -0500, Joel wrote:
> And from what I understand, this is caused when the Apache child exists
> and does not execute an explicit $dbh->disconnect() on the database
> handle. That is, the connection is not being closed properly before the
> handle goes out of scope.
That'
On Wed, 2004-12-22 at 13:15 +0100, Henning Meyer wrote:
> I understand this - but I want to use Apache::Registry for
> performance-reasons. How can I get different configurations in different
> Versions of my system?
> Should I use something like Config::Tiny?
> Or can I use Apache::PerlRun just
Hmm, I managed to get it to work with either -fpic or -fPIC after switching
to shared perl.
Also built with -m64.
I noticed Apache (at least 2.0.52) configures/compiles for -fPIC
automagically.
But once it loads, it is BIG.
(note lotta Apache modules, Apache::Request, CGI loaded via
Well you are not stating which mp-version you are running but for:
mp1:
http://perl.apache.org/docs/1.0/guide/modules.html#Apache__PerlVINC___Allows_Module_Versioning_in_Location_blocks_and_Virtual_Hosts
mp2:
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
Tom
Henning Me
> I understand this - but I want to use Apache::Registry for
> performance-reasons. How can I get different configurations in different
> Versions of my system?
> Should I use something like Config::Tiny?
> Or can I use Apache::PerlRun just for my config.pl - which I include via
> require 'config.
Arun pandey schrieb:
I guess the problem might be with your PerlHandler, coz Apache::Registry,
caches all scripts, as a result certain global values will remain
persistent. In such a case you might want to use Apache::PerlRun instead ,
which mimics mod_cgi by flushing the namespace at the every s
Juan Julian Merelo Guervos wrote:
Hi,
I must be a bit thick today, but I have thoroughly read the
Apache::AuthDBI documentation, and even the source, and I haven't
found any reference to where the username is put, once authenticated.
Can somebody help me?
Help thyself... it's, as was to be expe
Hi,
I must be a bit thick today, but I have thoroughly read the
Apache::AuthDBI documentation, and even the source, and I haven't found
any reference to where the username is put, once authenticated. Can
somebody help me?
JJ
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http:
20 matches
Mail list logo
