perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Tompkins" <>
Subject Re: Strange "Can't locate" errors
Date Wed, 05 Dec 2001 23:41:59 GMT
I've seen this happen on some NFS volumes on Solaris.  In this case the
problem was supported by 'ls' reporting different contents on the same
directory between two different shells.  Unfortunately, I'm not an NFS wiz
and I don't recall what the resolution was (yeah, I know... really helpful


Tim Tompkins
----- Original Message -----
From: "Robert Landrum" <>
To: <>
Sent: Wednesday, December 05, 2001 4:24 PM
Subject: Strange "Can't locate" errors

Can't locate CapWiz/Home/ in @INC (@INC contains: /data/ap/perl-
5.6.1/lib/5.6.1/sun4-solaris /data/ap/perl-5.6.1/lib/5.6.1
/data/ap/perl-5.6.1/lib/site_perl/5.6.1 /data/ap
/perl-5.6.1/lib/site_perl . /data/ap/capwiz-apache/
erl) at (eval 12) line 3.

Normally this error wouldn't be a problem for me...  Except..

[rlandrum@par-s01 Home]$ pwd
[rlandrum@par-s01 Home]$ ls -l
total 56
-r--r--r--   1 rlandrum content    27927 Nov 30 15:27

The file exists!

So it's there, and so are all it used modules.  Infact, I had this
working just a few hours ago with user rlandrum (on port 8083), but
once it fired up under root (on port 80), I started getting these

And I am definitly using the same httpd binary.

This is a:

SunOS 5.7 Generic_111437-01 sun4u sparc SUNW,Ultra-4
perl v5.6.1 built for sun4-solaris
Apache/1.3.22 (Unix) mod_perl/1.26

Any thoughts?


"Only two things are infinite: The universe, and human stupidity. And I'm
sure about the former." --Albert Einstein

View raw message