the permisions of the module and containing folder are 777

All parent directories up in the hierarchy also need to be accessible by the webserver, i.e. at least their 'x' bit must be set. Have you checked that? (this is often overlooked)

(BTW, don't get into the habit of setting files/directories world writeable without a good reason — it could bite you some time...)

Nope. I've given it the absolute path. And I've verified that it's looking there by printing @INC in the scripts output.

Could it be some weird permissions thing? Something to do with my apache config not allowing external perl modules if the module is someplace it doesn't like? ???

And how about you give us some actual code? And some paths? It could be a typo for all we know at the moment.

OK... I moved the folder containing the modules to a standard location, (/Library/Perl . I'm on OSX). It works fine in that folder. It's just inconvenient to develop in one folder and move stuff there.

I changed the permissions all the way up the tree of my user directory as a test, but it didn't help...

I'm absolutely sure there are no typos in the path. I've done the use lib thing before many times, just not with cgi. I'm new at the perl cgi part.

I really think it might have something to do with my apache server setup.

But anyway, I guess I'm just going to move it there for now, because I'm in a hurry to get some work done.

Thanks for the tips. I'll check back later in case anyone has any other thoughts.

I changed the permissions all the way up the tree of my user directory as a test, but it didn't help...  I'm absolutely sure there are no typos in the path.

In that case it could be restricted access due to some SELinux or AppArmor configuration (the latter is likely if the box is running a newer SUSE Linux).  It's hard to tell, though, as you haven't told us anything about the platform this is...  (Update: Sorry, I overlooked the OSX in your reply...)

I had a thought! I had two thoughts. They are:
• tell us if it works from the command line
• tell us what the code and the paths actually are

Oh and as for:

It's just inconvenient to develop in one folder and move stuff there.

So ... just don't do that then.

---




Nobody says perl looks like line-noise any more
kids today don't know what line-noise IS ...

So why does it say it can't find the module? I know it's there. The cgi script runs under user www, but the permisions of the module and containing folder are 777...

What do I do?

First, you post the exact error message here (inside <code> tags, mind you). Then we'll see.

I'd write a small CGI script which tries to open the module file in question (dying $!). If it barfs, I'd try to chdir where the module file lives, splitting the path and going down each folder. That would give clues.

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

#!/usr/bin/perl -w

use strict;
use CGI::Carp qw(fatalsToBrowser);
use Data::Dumper;

my $file = "/data/www/mods/foo.pm";

print $< , "\n";
print $> , "\n";
print $( , "\n";
print $) , "\n";

print Dumper(\@INC);

system('/bin/ls -dl /data');
system('/bin/ls -dl /data/www');
system('/bin/ls -dl /data/www/mods');
system('/bin/ls -dl /data/www/mods/foo.pm');

open FH, "<" . $file or die $!;
[download]