Perrin,
> You want something more like this:
>
> Alias /perl-bin/ "c:/IndigoPerl//perl-bin/"
> PerlModule Apache::Registry
>
>SetHandler perl-script
>PerlHandler Apache::Registry
>Options ExecCGI
>
Yup, this gets it working (It does need the line
"LoadModule perl_module modul
> I was also thinking it would only make a small
> difference, but I see many perl/CGI scripts that boast
> 'all this functionality in a single script'
They probably don't know any better, but to me that translates to "giant
bloated unorganized mess of a script."
> # BEGIN MOD_PERL CONFIG
> #Loa
Perrin,
Thanks for the response,
--- Perrin Harkins <[EMAIL PROTECTED]> wrote:
> No offense, but your script must not have been doing
> much in this test.
> The difference between putting everything in one
> script vs. using
> modules is just the time it takes to open and read
> the files. It's
> After I set up my app (webtool.cgi) and created the
> single script version (bigtool.cgi), I ran this script
> on my machine and it showed that the single file was
> about 10-15% faster than the multiple modules.
No offense, but your script must not have been doing much in this test.
The differ
I'd like to announce the release of Bricolage 1.2.0. It will shortly be
available for download from http://bricolage.sourceforge.net/. This
release features several bug fixes and quite a few important new
features. It uses HTML::Mason exlusively for its UI, and uses either
HTML::Mason or HTML::Tem
I was trying to test the CGI response time of a
Perl/CGI script under two conditions: as multiple
modules versus a single big script. First I installed
IndigoPerl (from indigostar.com) on my Windows machine
(which has an integrated apache server with mod_perl
enabled by default). Then I ran this
Perrin Harkins wrote:
>
> The difference is that Apache::Resource should apply this limit to each
> new child process. When you do this from the shell, you are limiting
> the parent Apache process, which isn't very useful.
I put
use BSD::Resource;
setrlimit RLIMIT_AS, 3200, 6400;
at t
Nevermind - I did a "make distclean" and started over, and now the
problem's gone. I still wonder what it means though.
--Bill.
William R Ward writes:
>
>This is weird... anyone ever seen this before? In the middle of
>compiling the modules, I get syntax errors in the C code??
>
>--Bill.
>
>
Hi,
I was recently accepted as the editor for the mod_perl category of the
Open Directory Project. The ODP is an all volunteer effort to build a
directory of the web. Check it out at http://dmoz.org or any number
of other services that use the underlying database (AOL, Google, etc.)
The mod_per
This is weird... anyone ever seen this before? In the middle of
compiling the modules, I get syntax errors in the C code??
--Bill.
/opt/SUNWspro/bin/cc -c -I/usr/local/include -O-DVERSION=\"1.00\"
-DXS_VERSION=\"1.00\" -KPIC -I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE Leak.c
"Leak
Geoffrey Young <[EMAIL PROTECTED]> writes:
> William R Ward wrote:
> >
> > The Apache server processes its config file twice when starting up,
> > and our code doesn't react well to that. On the first pass,
> > everything initializes hunky-dorily (if that's a word), but on the
> > second pass lo
Documentation for these functions reads as follows:
$r->get_basic_auth_pw
If the current request is protected by Basic authentication, this
method will return 0, otherwise -1. [snip]
$r->note_basic_auth_failure
Prior to requiring Basic authentication from the client, this method
will set the out
> What are the basic advantages, disadvantages, and limitations of:
> (a) stuffing all this setup/framework code into a module (either a new
module or subclassing Apache::RegistryNG as you mention below),
> versus,
> (b) stuffing it into a handler that all requests for a large subset of
the pages
At 06:56 PM 01/10/02 +0300, [EMAIL PROTECTED] wrote:
>Hello!
>
>I'm getting lots of errors in log:
>
>[Thu Jan 10 18:54:33 2002] [notice] child pid 8532 exit signal Alarm clock
>(14)
I hope I remember this correctly:
What's happening is you are setting a SIGALRM handler in perl, but perl is not
At 09:09 PM 1/9/2002 -0500, Perrin Harkins wrote:
>Normal Perl rules apply. Modules are good for sharing code. You could
>stuff the shared parts into a sub in a module that every script would
>call. Or you could use an OO approach, with a base class that holds all
>of the boiler-plate stuff.
Can Apache::Reload be used to reload modules that are "use"-d by httpd PerlModule,
PerlRequire, or PerlHandler directives, or do they have to be explicitly "use"-d in
code that is inside a handler? I think the answer is "yes - these are no different
than anything else except that memory sharing
Hello!
I'm getting lots of errors in log:
[Thu Jan 10 18:54:33 2002] [notice] child pid 8532 exit signal Alarm clock
(14)
[Thu Jan 10 18:54:37 2002] [notice] child pid 8542 exit signal Alarm clock
(14)
[Thu Jan 10 18:54:42 2002] [notice] child pid 8537 exit signal Alarm clock
(14)
What causes t
> hrm. the problem might not be the double-loading of httpd.conf then -
> that's been around since, well, before most of us (I tracked that down
> to apache 0.9 once through list archives)
>
> more likely is this:
> http://marc.theaimsgroup.com/?l=apache-modperl&m=100510779912574&w=2
>
> and th
El Mié 09 Ene 2002 18:16, William R Ward escribió:
> The Apache server processes its config file twice when starting up,
> and our code doesn't react well to that. On the first pass,
> everything initializes hunky-dorily (if that's a word), but on the
> second pass lots of stuff that is assumed t
William R Ward wrote:
>
> The Apache server processes its config file twice when starting up,
> and our code doesn't react well to that. On the first pass,
> everything initializes hunky-dorily (if that's a word), but on the
> second pass lots of stuff that is assumed to be loaded in memory
> do
The Apache server processes its config file twice when starting up,
and our code doesn't react well to that. On the first pass,
everything initializes hunky-dorily (if that's a word), but on the
second pass lots of stuff that is assumed to be loaded in memory
doesn't work.
This has been working
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 enco
Not long ago, John Buwa proclaimed...
> I havea question on outbound ips. I am writing a program that a user can
> enter an address and a spider will go and retrieve only the information that
> was request and then display the results to the enquiring user. My question
> is though, i have grabed t
Benoit Caron wrote:
>
> 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 (REFE
Sorry - I forgot to say that after I reinstalled apache in included
"AddModule mod_perl.c" it all worked okay
cheers
Dan
-Original Message-
From: C.Hauser - IT assistance GmbH [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 10, 2002 10:09 PM
To: Dan Horne
Subject: Re[2]: Installing m
CU, cheers for this -
2 Things:
1. I reinstalled apache in c:/apache
2. I added "AddModule mod_perl.c" as you mentioned below. I did try with my
old installation, but it didn't seem to parse. I don't know what was
different this time other than my installation directory
Thanks again
Dan
---
> The installation of mod_perl (from theoryx5.uwinnipeg.ca) via ppm fails when
> it attempts to install mod_perl.so to c:\apache root. The default location
> for apache when I installed it was c:\program files\apache group\apache. I
> followed the instructions and manually copied mod_perl.so to m
Hi all
I have just installed the binary of Apache v1.3.22 on Windows 2000 and have
attempted to add mod_perl. I am using ActiveState Perl 5.6.1
The installation of mod_perl (from theoryx5.uwinnipeg.ca) via ppm fails when
it attempts to install mod_perl.so to c:\apache root. The default location
28 matches
Mail list logo
