Matt,

Thank you very much for your input.  Our "usual" path for perl (perl5) is
in /usr/local/lib.  When we installed SA (and the razor), we identified 
/usr/local/lib as the path (instead of /usr/lib).  I checked for other
copies on our system, and there don't seem to be any.

I know that these files exist in one of the razor-agents directories -
is there any way we can manually install these files? (i.e., just
copy them over instead of 'installing' them through the makefile/perl).?

Thanks to you, or anyone else who responds.

Robert


/.r.\

On Mon, 8 Sep 2003, Matt Kettler wrote:

> Date: Mon, 08 Sep 2003 10:22:30 -0400
> From: Matt Kettler <[EMAIL PROTECTED]>
> To: Robert Amodeo <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: [Razor-users] the usual "Can't locate .. " "Razor2" problem
> 
> At 04:08 PM 9/5/2003 -0700, Robert Amodeo wrote:
> 
> >If it's looking for Agent.pm, why wouldn't it be installed in the perl
> >library?
> 
> is it in /usr/lib/perl5/site_perl  instead 
> of  /usr/local/lib/perl5/site_perl (where SA is looking)?
> 
> I've encountered this situation on one of my machines, and several other 
> people have had the same problem when installing SA via CPAN. If you've got 
> a buggy version of CPAN, it decides to upgrade perl and it downloads and 
> installs a second copy of perl in /usr/local, and puts SA there..
> 
> This means that the rouge copy of SA, unintentionally installed in 
> /usr/local/*, can't find anything that's installed in the original copy of 
> perl, which is in /usr/*.
> 
> Check for it, if that's not it, post a follow up message. I don't think 
> I'll have any further ability to help you if this isn't your problem, but 
> at that point someone else might be able to.
> 
> 



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Razor-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/razor-users

Reply via email to