I wrote a CGI script like this: #!/usr/bin/perl -w use CGI ":standard"; sleep 10; print header(), start_html(), end_html(); and saved it in the appropriate place with a .pl extension. When it runs the server creates a new Perl process which exists for 10 seconds. I.e. it runs as a normal forked CGI process, not a mod_perl one. The test link you gave tells me mod_perl is working on my system. Have I missed something?
So, if mod_perl is installed, Apache will use mod_perl for scripts ending on ".pl".
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 01:03 PM 06/15/00 +0100, Derek Fountain wrote:
I wrote a CGI script like this:
#!/usr/bin/perl -w use strict; # left out a line ;)
use CGI ":standard";
sleep 10; print header(), start_html(), end_html();
and saved it in the appropriate place with a .pl extension. When it runs the server creates a new Perl process which exists for 10 seconds. I.e. it runs as a normal forked CGI process, not a mod_perl one.
What is the "appropriate place"? To run it as An Apache::Registry script
you would need to make sure that the correct handler is set for your
script, in the correct directory, file, or URL (location). If I remember
correctly from the past post, it was only .pl files in the cgi-bin directory.
For example, for all files named test.pl
<files test.pl>
SetHandler perl-script
PerlHandler Apache::Registry
Options ExecCGI
allow from all
# Don't need this with CGI.pm, but it won't hurt.
PerlSendHeader on
</files>
Or for all URL requests starting with /perl (as set in an Alias directive)
participants (2)
-
fountai@hursley.ibm.com
-
moseley@hank.org