It's actually:
PerlSetVar PerlRunOnce On
(that's without the handler, of course. With it you want that off)
Andrew Chen
Intern, Architecture
[EMAIL PROTECTED]
206-219-8445
The Cobalt Group, Inc.
On Tue, 1 Aug 2000, Pramod Sokke wrote:
> Where did you set your PerlRunOnce option? I tried setting it in httpd.conf
> like this:
>
> Alias /cgi-perl/ /usr/ns-home/cgi-bin/
> <Location /cgi-perl/>
> #AllowOverride None
> SetHandler perl-script
> PerlHandler Apache::PerlRun
> Options +ExecCGI
> allow from all
> PerlSendHeader On
> PerlRunOnce On
> </Location>
>
> and I got this error:
>
> Invalid command 'PerlRunOnce', perhaps mis-spelled or defined by a module
> not included in the server configuration.
>
> -Pramod
>
> At 04:25 PM 7/25/00 -0700, Andrew Chen wrote:
> >On Tue, 25 Jul 2000, Pramod Sokke wrote:
> >
> >> Andrew,
> >> >From your discussion on the forum, I recall you mentioning the differences
> >> between PerlRunOnce being 'On' and 'Off'. Since our code is extremely
> >> shabby and huge, will I be able to use it with 'Off'? If I don't, will I be
> >> compromising on the speed?
> >>
> >> Thanks again for the great detailed write-up!
> >> -Pramod
> >
> >If PerlRunOnce is On, then you can use your code without any changes, even
> >if it is completely horrible. PerlRunOnce Off allows for bigger speed
> >increases, but then you have to write the handler.
> >
> >If you just want a really quick speed improvement, stick it on PerlRun
> >with PerlRunOnce On and see if that's sufficient.
> >
> >If you feel like writing the handler (so that you can get a really big
> >speed boost) then you can run it with PerlRunOnce Off.
> >
> >Andrew
>
