Is anyone using mod-perl with apache-1.3.14 on RedHat 7.0? Any complaints?
Jamie Krasnoo
On Mon, 8 Jan 2001, Joshua Chamas wrote:
Hey,
I like the idea of Apache::SizeLimit, to no longer worry about
setting MaxRequestsPerChild. That just seems smart, and might
get maximum usage out of each Apache child.
What I would like to see though is instead of killing the
child based on
What I would like to see though is instead of killing the
child based on VmRSS on Linux, which seems to be the apparent
size of the process in virtual memory RAM, I would like to
kill it based on the amount of unshared RAM, which is ultimately
what we care about.
We added that in, but
Perrin Harkins wrote:
We added that in, but haven't contributed a patch back because our hack only
works on Linux. It's actually pretty simple, since the data is already
there on Linux and you don't need to do any special tricks with remembering
the child init size. If you think it would
I was rewriting the detecting 'STOP' button pressed section in the guide,
to notice that Apache::SIG kills the process under Apache::Registry.
httpd.conf:
PerlFixupHandler Apache::SIG
test script:
use strict;
my $r = shift;
$r-send_http_header('text/plain');
print("PID = $$\n");
Jamie Krasnoo wrote:
Is anyone using mod-perl with apache-1.3.14 on RedHat 7.0? Any complaints?
Me, core dumps.
I recompiled perl_5.005_03 ,apache_1.3.12, mod_perl-1.24 and now
it works:
$ perl -v
This is perl, version 5.005_03
$ telnet localhost 80
Trying 127.0.0.1...
Connected to
there were some problem reports when 7.0 was first released - I don't think
any of those resulted in resolutions sent to the list...
from what I've heard, the gcc that ships with 7.0 had some real problems - I
dunno the current status, though...
--Geoff
-Original Message-
From: Jamie
We are working on a dynapage engine that can be operated under mod perl.
The system works well when ran under configuration such as
Location /pgc
SetHandler perl-script
PerlHandler PGC:;Handler
/Location
however when we try to use
Location /
SetHandler perl-script
PerlHandler
You wrote:
Date: Tue, 9 Jan 2001 00:16:46 +0530
To: [EMAIL PROTECTED]
From: "Siddhartha Jain" [EMAIL PROTECTED]
Subject: Re: mod-perl on Solaris 2.6
Message-ID: 00c201c079a3$5a678de0$1a01010a@Sid
Applying patches was the first thing i did after installing the OS (kind
of
a standard
Hi,
I use apache1.3.12 with mod_perl 1.24 and I've been using it in several
programs with DBI (version 1.13). This is the first time I get an error
like this, other programs that uses DBI are still working.
In command line everything is working ok, but when I run my
I'm looking for Boston area companies, or possibly something that can be
done on a telecommuting basis, requiring expertise with perl (modperl) and
apache in a large-scale environment.
I've got some pretty good experience using modperl, please email me for a
resume. I'm mainly targeting
-Original Message-
From: Jacqui Caren [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 8:06 AM
To: Mod Perl
Cc: Oliver Taylor; Jacqui Caren
Subject: Adding a mod_perl / handler gives odd SCRIPT_NAME and
PATH_INFO...
The problem is that we expect everything
Jamie Krasnoo wrote:
Is anyone using mod-perl with apache-1.3.14 on RedHat 7.0? Any complaints?
Francesc Guasch wrote:
Me, core dumps.
-
Well, I'm trying to as well. I have:
RedHat 7.0
Apache-1.3.14
Perl-5.6.0
mod_perl-1.24_01
Berkeley-3.1 (seemed required to get Sendmail
Jacqui Caren ([EMAIL PROTECTED]) said something to this effect on 01/09/2001:
Location /pgc
SetHandler perl-script
PerlHandler PGC:;Handler
^
/Location
* snip *
Location /
SetHandler perl-script
PerlHandler PGC:;Handler
^
/Location
* snip
Hi,
Finally, i have it working. Thanks to all those who replied. Although, i
still don't know the exact cause of the previous failures but i suspect it
was threaded perl builds cause some debugging thru' gdb shows something
related to threads. Unfortunately, i deleted the debug dump. Anyway,
On Tue, 9 Jan 2001 10:45:11 -0500, darren chamberlain wrote:
Jacqui Caren ([EMAIL PROTECTED]) said something to this effect on 01/09/2001:
Location /pgc
SetHandler perl-script
PerlHandler PGC:;Handler
^
/Location
* snip *
Location /
SetHandler
I have one problem that realy is more of an annoyance than a threat. I've
mentioned it before and realy got no solutions as to why this happens. On
RedHat 7.0 when I have mod_perl-1.24_01 compiled in to apache-1.3.14 and
have a PerlRequire set to startup.pl. It (startup.pl) seems to get run
Hi there,
On Tue, 9 Jan 2001, Jamie Krasnoo wrote:
(startup.pl) seems to get run twice.
Isn't this mentioned in the Guide?
73,
Ged.
#Location Handlers
Location
PerlAccessHandler Apache::GateKeeper
/Location
The Location directive needs to specify a URL to which it applies:
Location /
Perl*Handlers can go pretty much anywhere, as long as the server
administrator hasn't diabled .htaccess files.
On Tue, 9 Jan 2001, Joshua Chamas wrote:
Perrin Harkins wrote:
We added that in, but haven't contributed a patch back because our hack only
works on Linux. It's actually pretty simple, since the data is already
there on Linux and you don't need to do any special tricks with
Hi there,
On Tue, 9 Jan 2001, Joseph Crotty wrote:
open(FILE, "/tmp/dog");
Always check the status returned by a call like open().
73,
Ged.
Good advice Ged. I figured out the problem...there was another server
running on the port almost exactly like the one I was using, but without the
PerlAccessHandler. Huge brain fart. I need a nap.
-Original Message-
From: G.W. Haywood [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January
--
mod_perl digest
January 1, 2001 - January 6, 2001
--
Recent happenings in the mod_perl world...
Features
o
I like the idea of Apache::SizeLimit, to no longer worry about
setting MaxRequestsPerChild. That just seems smart, and might
get maximum usage out of each Apache child.
What I would like to see though is instead of killing the
child based on VmRSS on Linux, which seems to be the
IMHO, he has a point. I'd also benefit from memory usage based upon an application
threshold. He has a good idea...
Rob Bloodgood wrote:
I have a machine w/ 512MB of ram.
unload the webserver, see that I have, say, 450MB free.
So I would like to tell apache that it is allowed to use at
On Tue, 9 Jan 2001, Rob Bloodgood wrote:
I like the idea of Apache::SizeLimit, to no longer worry about
setting MaxRequestsPerChild. That just seems smart, and might
get maximum usage out of each Apache child.
What I would like to see though is instead of killing the
child
Hi,
well, almost... either change that to a Files directive or remove the
filename from the Location directive, so that Apache::Request applies to
all scripts within cgi-bin...
see http://perl.apache.org/guide/config.html for more details...
thank you for your reply. I have changed Files
On Tue, 9 Jan 2001, Al Abdullaev wrote:
I am a little bit confused. In the description of the
process of how to install without root access it is said
that I need to "The simplest approach is to simulate the
portion of the / file system relevant to Perl under your
home directory", What does
Hi Allysson,
On Tue, 9 Jan 2001, Allysson Flavio wrote:
Is there a way to put in our client's server only compiled scripts
or like??? Or can we change Perl source code to decript our files??
I think you'd better read a book about C.
Hi everybody else,
Just asking, but am I the only one
perldoc -q hide
Hello,
AFWe're developing a web based system here in Brazil for a Telecom
AFEnterprise. The mod_perl was the choice of our efforts create this web
AFbased system. We've already develope something in Perl and it was the
AFeasiest way to work with internet. But now there is a problem. To this
Allysson Flavio [EMAIL PROTECTED] writes:
We're developing a web based system here in Brazil for a Telecom
Enterprise. The mod_perl was the choice of our efforts create this
web based system. We've already develope something in Perl and it was
the easiest way to work with internet. But
"G.W. Haywood" [EMAIL PROTECTED] writes:
Hi Allysson,
On Tue, 9 Jan 2001, Allysson Flavio wrote:
Is there a way to put in our client's server only compiled scripts
or like??? Or can we change Perl source code to decript our files??
I think you'd better read a book about C.
Hi
I've lost the original email, but this is reply from Doug to my
email. I've asked to confirm that PERL5LIB is ignored with PerlTaintMode
is on. Apparently the Perl docs say a different thing...
Anybody has any insights about this situation? Does it has anything to do
with Perl versions?
Thanks!
At 21:24 09/01/2001 +, G.W. Haywood wrote:
Just asking, but am I the only one that gets a really bad feeling when
people want to use Open Source Software to do things like this? It
seems kinda counter to the spirit of it all somehow.
Please let us avoid the traditional flamewar that follows
On Tue, 9 Jan 2001, G.W. Haywood wrote:
Hi Allysson,
On Tue, 9 Jan 2001, Allysson Flavio wrote:
Is there a way to put in our client's server only compiled scripts
or like??? Or can we change Perl source code to decript our files??
I think you'd better read a book about C.
Hi
when I run make to install mod_perl
i get error saying that argument list is too long, and give me error 127
what does it all mean? should I ignore it and continue with make install??
Does anyone know if there is a module that enables dynamic cache
allocation for apache web server on the proxy?
On Tue, 9 Jan 2001, Elman Vagif Abdullaev wrote:
when I run make to install mod_perl
i get error saying that argument list is too long, and give me error 127
what does it all mean? should I ignore it and continue with make install??
You cannot expect your question answered if you don't
In upgrading to 1.24_01 I notice some warnings when the apache starts
that I don't remember being present.
Specifically resulting from the inclusion of perl handlers i.e.
PerlRequire /usr/local/apache/libhandlers/client23.pm
where the identical handler is used for both http and https
On Tue, 9 Jan 2001, Elman Vagif Abdullaev wrote:
Does anyone know if there is a module that enables dynamic cache
allocation for apache web server on the proxy?
"Dynamic cache allocation" could mean anything. Can you be more specific?
- Perrin
Alexander Farber wrote:
However I have this strange problem now: the web page doesn't change
until I reload it. (Un)commenting "PerlSendHeader On" doesn't help.
The only ways to see the expected results (like the initial empty web
form, when entering http://localhost/cgi-perl/file_upload.pl
I'm having trouble getting a script that uses the DBI module to work under
mod_perl. It works fine at the command line or as a normal cgi script.
I've included the code below. When I try to run from the browser under
mod_perl the only only output is the first portion of HTML. I've tried
On Tue, 9 Jan 2001, Rob Bloodgood wrote:
I have a machine w/ 512MB of ram.
unload the webserver, see that I have, say, 450MB free.
So I would like to tell apache that it is allowed to use at most 425MB.
I was thinking about that at some point too. The catch is, different
applications have
I am using a CPAN module called Socket::PassAccessRights
that uses the recvmsg and sendmsg system calls to pass
file descriptors over a socket. More specifically, I have a
long living program (not modperl) that needs to communicate
with the Apache descriptors for STDIN and STDOUT given to a CGI
because then all of your hard work before goes RIGHT out the window,
and I'm talking about a 10-15 MB difference between JUST FINE and
DEATH SPIRAL, because we've now just crossed that horrible, horrible
threshold of (say it quietly now) swapping! shudder
That won't happen if you use a
On Tue, 9 Jan 2001, Rob Bloodgood wrote:
OK, so my next question about per-process size limits is this:
Is it a hard limit???
As in,
what if I alloc 10MB/per and every now then my one of my processes spikes
to a (not unreasonable) 11MB? Will it be nuked in mid process? Or just
On Tue, 9 Jan 2001, Rob Bloodgood wrote:
OK, so my next question about per-process size limits is this:
Is it a hard limit???
As in,
what if I alloc 10MB/per and every now then my one of my
processes spikes
to a (not unreasonable) 11MB? Will it be nuked in mid process? Or just
Well right now proxy caching have static cache allocation, i.e. it caches
whatever the last request was asking for. But what I mean by dynamic
caching is to have some sort of script or module that will check if the
data stored on the proxy server is outdated. It will check if the data in
the
On Mon, Jan 08, 2001 at 11:48:36PM -0800, Joshua Chamas wrote:
UNSHARED_SIZE = CURRENT_SIZE - CHILD_INIT_SIZE
How would that account for pages that were shared post forked, but later
copied-on-write?
- Barrie
Hi there,
On Tue, 9 Jan 2001, Michael wrote:
In upgrading to 1.24_01 I notice some warnings when the apache starts
that I don't remember being present.
Constant subroutine con redefined at /usr/lib/perl5/constant.pm line 91.
I know it says perl5 in that path, but what version
On Tue, 9 Jan 2001, Rob Bloodgood wrote:
It's not a hard limit, and I actually only have it check on every other
request. We do use hard limits with BSD::Resource to set maximums on CPU
and RAM, in case something goes totally out of control. That's just a
safety though.
chokes JUST a
Is there any way to distinguish between a child being shutdown (say
maxrequests has been exceeded) versus all of Apache going down (kill
signal sent to the original process or something).
The reason I ask is that while I can do:
BEGIN
{
# make a file
}
I can't do:
END
{
# delete a
richter 01/01/07 20:24:39
Modified:embperl Changes.pod.1.html Changes.pod.10.html
Changes.pod.11.html Changes.pod.12.html
Changes.pod.13.html Changes.pod.14.html
Changes.pod.15.html Changes.pod.16.html
54 matches
Mail list logo
