<?xml version="1.0" encoding="windows-1252"?>
<node id="994270" title="Re^3: CGI script connecting via terminal but not via browser" created="2012-09-18 08:09:51" updated="2012-09-18 08:09:51">
<type id="11">
note</type>
<author id="597736">
aaron_baugher</author>
<data>
<field name="doctext">
&lt;p&gt;
The PATH environment variable only affects which perl executable is used, if there happens to be more than one on the system.  For instance, if you have &lt;c&gt;/usr/local/bin/perl&lt;/c&gt; and &lt;c&gt;/usr/bin/perl&lt;/c&gt;, the former will be picked up first by your shell, while the latter is used by your CGI.  Two different perls, even if the same version, could have two different sets of modules and configurations.  You could add &lt;c&gt;which perl&lt;/c&gt; to my test CGI to report the full pathname of perl, and the results of &lt;c&gt;perl -v&lt;/c&gt; will also show any differences in configs and the paths that perl checks for modules.  If those match, then PATH doesn't matter beyond that.
&lt;/p&gt;




&lt;div class="pmsig"&gt;&lt;div class="pmsig-597736"&gt;
&lt;p&gt;Aaron B.&lt;br /&gt;
Available for small or large Perl jobs; see my home node.
&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
994237</field>
<field name="parent_node">
994253</field>
</data>
</node>
