in reply to Re^2: apache2 passing PERL5LIB environment to cgi
in thread apache2 passing PERL5LIB environment to cgi

Hmm, never used perl with apache without mod_perl before. Does it start a new perl instance on every cgi call? So at least you get response from the script right? I mean as HTML in a browser. When you print @INC after your use lib line, do you see your $HOME/lib/perl5 in there? Was just wondering if ENV{$HOME} actually would have the right path or would show up something like /home/nobody/lib/perl5 or /lib/perl5?
  • Comment on Re^3: apache2 passing PERL5LIB environment to cgi

Replies are listed 'Best First'.
Re^4: apache2 passing PERL5LIB environment to cgi
by Anonymous Monk on Jun 15, 2010 at 07:42 UTC
    Does it start a new perl instance on every cgi call?

    The definition of CGI is start a new instance on every call, read input (form data or whatever) from STDIN, read headers from %ENV, write output on STDOUT.

      Erm... I guess I should've clarified, afaik when you are using mod_perl that gives you a built in interpreter in the apache server as a module so your apache instance doesn't have to call the external perl executable every time it encounters a call to a CGI written in perl.