I understand that mod_jk is more efficient than mod_jserv. My sysadmin has
not complained about any problems integrating mod_perl or mod_jk (but then
mod_jk is in the front-end as stated below where mod_perl is in the backend
apache server).
At 01:18 AM 1/18/2001 -0600, Les Mikesell wrote:
Due to a number of notes about how hard it was to install this beast, I've
really worked hard this time to get all of the wrinkles out of the
installer and I think its pretty good now.
This release (actually 1.05, but I didn't announce that here) adds
get_headers() to get a list of the returned
I know we've been over this before, but I think I've forgotten!
How do I detect if Apache::Log got compiled in a module's Makefile.PL ?
I can't do eval("use Apache::Log;") because Apache/Log.pm gets installed
regardless, its just that the Log.so doesn't get compiled. So, how do I do
it?
--
Perrin Harkins wrote:
On Wed, 17 Jan 2001, ___cliff rayman___ wrote:
i and others have written on the list before, that pushing apache
children into swap causes a rapid downward spiral in performance. I
don't think that MaxClients is the right way to limit the # of
children. i think
I'm not subscribed to this mailing list, but I searched the archives for
this patch and found no direct answers, only references to the current
modperl in CVS. I extracted the relevant pieces into a patch and thought
other people would have the same problem and would benefit from this patch.
So
you just needed mod_perl-1.24_01.
you can get it at:
http://perl.apache.org/dist/
apparently the underscore in the patch level keeps it
from showing up as the latest release in CPAN.
cliff
Dave Dykstra wrote:
I'm not subscribed to this mailing list, but I searched the archives for
this
(In the post below, 'STDIN', 'STDOUT', and 'STDERR' refer to Perl
filehandles, while 'stdin', 'stdout', and 'stderr' refer to Perl file
descriptors.)
During migration of a web application server from Perl 5.00503 to Perl
5.6, we discovered a bug in mod_perl 1.23 and above. Under Perl 5.6,
On Fri, 19 Jan 2001, Matt Sergeant wrote:
Do we have anything holding us up from releasing 1.25 ?
same stuff i mentioned last week when vivek asked. but more likely to be
ready next week.
Hi folks!
I have just seted mod_perl with apache and i am using embperl too.
I am worried about security concerns for mod_perl.
How can i limit, for instance, the amount of memory used for embperl?
the ammount of time allowed for a perl code to spend. With php is easy,
there is directives like
- Original Message -
From: "Sam Horrocks" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: "mod_perl list" [EMAIL PROTECTED]; "Stephen Anderson"
[EMAIL PROTECTED]
Sent: Thursday, January 18, 2001 10:38 PM
Subject: Re: Fwd: [speedycgi] Speedycgi scales better than mod_perl withsc
ripts that
My insanely simple and useful module Apache::DumpHeaders got a few
more tiny iterations. One of these days I'll update the
documentation and call it 1.00. It is after all more than a year
since I adopted Doug's then 10 line handler. :)
The URL
On Thu, 18 Jan 2001, Matt Sergeant wrote:
[...]
This release (actually 1.05, but I didn't announce that here) adds
get_headers() to get a list of the returned headers from the request in
the order they came in. I believe some people here asked for that.
Ah, that makes me feel bad. Chris
We have a Perl CGI application that used to run on a Netscape server.
It was using a proprietary system to compile once and run many.
We recently moved to Apache, but we are having problems with page
loading and reloading.
With a Netscape (4.7) browser when you first load a page (not cached)
it
13 matches
Mail list logo
