Hello can some help me pelase?
i've recently installed Apace 1.3.22...i've configured the
CGI directive to work as well
but when i try to execute a CGI script written in perl
that message appears:
Internal Server Error
The server encountered an internal error or
misconfiguration and was
On Wed, 9 Jan 2002, Alan Civita wrote:
More information about this error may be available in the
server error log
Try reading the text :-)
--
!-- Matt --
:-Get a smart net/:-
Alan Civita wrote:
Hello can some help me pelase?
i've recently installed Apace 1.3.22...i've configured the
CGI directive to work as well
but when i try to execute a CGI script written in perl
that message appears:
Internal Server Error
The server encountered an internal error or
is it possible that i have to do something special
in compiling apache to activate the perl mode?
Alan Civita wrote:
is it possible that i have to do something special
in compiling apache to activate the perl mode?
have you read at perl.apache.org? or about executing cgi's in apache?
/Jon
Alan Civita wrote:
Surely...
and I've done all of it...
..have i to use sonme particular option during the
configuration and installation of apache in order to
use/enable the perl in Apache?
thx again
Alan,
For basic CGI under apache, you will need to make sure your scripts
print out the
El Mié 09 Ene 2002 10:00, Alan Civita escribió:
Hello can some help me pelase?
i've recently installed Apace 1.3.22...i've configured the
CGI directive to work as well
but when i try to execute a CGI script written in perl
that message appears:
Internal Server Error
The server encountered
On Wed, 9 Jan 2002, cloudor wrote:
I get the message shown as [error] Cannot remove module
mod_perl.c: not found in module list when i restart apache
after installing mod_perl and adding LoadModule perl_module
modules/mod_perl.so in the httpd.conf .
[ ... ]
Do you have a directive
hi...
I use BSD::Resource to limit the RAM a mod_perl process could get. this
works perfectly right on one machine but on another the process does not
get any RAM at all and is killed immediately. both servers run under
linux and therefor I use RLIMIT_AS as described in the mod_perl guide
from
has anybody any ideas?
Apache::Resource.
Gunther Birznieks wrote:
Is this a lot different from PlRPC?
Perhaps this should be a transport layer that is added to PlRPC rather than
creating a brand-new service?
Ideally it would be nice if it were architected with mod_perl and HTTP
being the default mechanism of transport but that
The following short test script :
#!/usr/local/bin/perl
use strict;
use Apache;
my $r = shift;
my %params = $r-method eq 'POST' ? $r-content : $r-args;
$r-send_http_header('text/html');
print Name = [, $params{'Name'}, ]br /;
print R = [ , $r, ]br /;
print Mehtod = [, $r-method, ]br /;
print
[EMAIL PROTECTED] wrote:
Hi all,
I'm having an odd problem with a particular registry script.
This script causes a segmentation fault at the first usage of
Apache::Util::escape_uri(),
This same script also uses Apache::Util::escape_html() with no problems
at all.
Other scripts
On Wed, 9 Jan 2002, Mark Maunder wrote:
The difference is that AppCluster allows you to call
multiple remote methods on the server (or on multiple
distributed servers) simultaneously. However, I wasn't
aware of PlRPC and I really like the interface i.e. the
way it creates a copy of the
brian moseley wrote:
On Wed, 9 Jan 2002, Mark Maunder wrote:
The difference is that AppCluster allows you to call
multiple remote methods on the server (or on multiple
distributed servers) simultaneously. However, I wasn't
aware of PlRPC and I really like the interface i.e. the
way
On Wed, 9 Jan 2002, Mark Maunder wrote:
Well, I guess two methods could be added to the client
object. One to add a concurrent request to be called
(register_request()) and one to send all registered
requests concurrently. I'm not the author though, so
you'll have to chat to Jochen about
Background:
I'm working on a site that is a mix of php (which I'm gradually converting to
mod_perl) and mod_perl (running under Apache::Registry and using Template Toolkit
(TT2)) using an apache configuration like this:
Directory /
[...]
Files *.par
SetHandler perl-script
I'm trying to set a way of passing some environnement variables from my
front-end server to my back-end so that my Registry or PerlRun script run
unchanged. What I've done is that I've modified my frontend to add, with
mod_rewrite, the environnement data I need (REFERER and REMOTE_ADDR), and
brian moseley wrote:
On Wed, 9 Jan 2002, Mark Maunder wrote:
Well, I guess two methods could be added to the client
object. One to add a concurrent request to be called
(register_request()) and one to send all registered
requests concurrently. I'm not the author though, so
you'll
Thanx, but that leads to the same result. In the first place I used:
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_AS 32:64
PerlChildInitHandler Apache::Resource
in httpd.conf, but Apache::Resource uses BSD::Resource in the end and
thus its the same as
use BSD::Resource;
setrlimit
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_AS 32:64
PerlChildInitHandler Apache::Resource
in httpd.conf, but Apache::Resource uses BSD::Resource in the end and
thus its the same as
use BSD::Resource;
setrlimit RLIMIT_AS, 3200, 6400;
The difference is that
There are many *.par pages (estimate: 70-100 when conversion is
complete),
and they all contain the following code with minor variations that
could be
made consistent (like what constants are imported, what modules are
used,
etc.). I'd like to find a way to prevent having that code (below)
Yeah, it helps. Thank you!
Best Regards,
Cloudor Pu
[EMAIL PROTECTED]
2002-01-10
Randy Kobes wrote a letter at 2002-01-09 09:14:00 £º
On Wed, 9 Jan 2002, cloudor wrote:
I get the message shown as [error] Cannot remove module
mod_perl.c: not found in module
23 matches
Mail list logo
