Hi Hugh,

Thanks for providing inforamtion for my question.

I know I had better build a newer perl on my target machine but there are
some practical reasons which forbid me to do so.

Is it recommandable to compile and run radius server against a new version
of perl, say /usr/local/bin/perl5.00503, in stead of the default
/usr/local/bin/perl which is a problematic 5.00404 version?

I have tried this approach but it failed. I found that radiusd is
hardcoded to use /usr/local/bin/perl. However even though I change radiusd script to 
use
 /usr/local/bin/perl5.00503, the radius server still manifests the same 
odd behaviors.

Should I continue to work on this approach? Has this approach ever been
worked out successfully? 

Jason


On Sun, 20 Feb 2000, Hugh Irvine wrote:

> 
> Hello Jason -
> 
> On Sun, 20 Feb 2000, Jason Kao wrote:
> > Hi,
> > 
> > I am using Radiator-2.14.1, SunOS 5.7 Generic_106541-04
> > sun4u sparc SUNW,Ultra-1 and perl version 5.005_02 built for
> > sun4-solaris-thread. Radius server run well.
> > 
> > 
> > I run the Radius on the production machine which has older perl and
> > OS. SunOS 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-Enterprise  perl,
> > version 5.004_04 built for sun4-solaris.
> > 
> > The radius starts manifesting very odd behaviors in my production
> > machine which has perl 5.004_04 and SUNOS 5.6. 
> > 
> > Is there any problems that the perl's version and OS's version might
> > cause?
> > 
> 
> We have seen many problems caused by exactly this. You are always better to
> build the latest stable version of Perl on your target machine and then install
> everything else from scratch. The latest stable version of Perl on www.perl.com
> is Perl 5.005_03.
> 
> regards
> 
> Hugh
> 
> -- 
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
> NT, Rhapsody
> 


===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to