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 :o)
Regards, Tim Tompkins ---------------------------------------------- Programmer http://www.arttoday.com/ http://www.rebelartist.com/ ---------------------------------------------- ----- Original Message ----- From: "Robert Landrum" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 05, 2001 4:24 PM Subject: Strange "Can't locate" errors Can't locate CapWiz/Home/App.pm 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/l ib/site_perl/5.6.1/sun4-solaris /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/ /data/ap/capwiz-apache/lib/p erl) at (eval 12) line 3. Normally this error wouldn't be a problem for me... Except.. [rlandrum@par-s01 Home]$ pwd /data/ap/perl-5.6.1/lib/site_perl/5.6.1/CapWiz/Home [rlandrum@par-s01 Home]$ ls -l total 56 -r--r--r-- 1 rlandrum content 27927 Nov 30 15:27 App.pm 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 errors. 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? Rob -- "Only two things are infinite: The universe, and human stupidity. And I'm not sure about the former." --Albert Einstein
