Hello Erich -
My usual suggestion is to keep the source distributions in seperate directories and run "radiusd" from there.
Something like this:
mkdir /usr/local/src/Radiator
cd /usr/local/src/Radiator
mv /tmp/Radiator-3.8.tgz .
gzip -c -d Radiator-3.8.tgz | tar xvf -
cd Radiator-3.8
perl Makefile.PL
make
make test
***DO NOT*** make installNow you can run "radiusd" from the distribution directory:
perl radiusd -foreground -log_stdout -trace 4 -config_file /your/configuration/file
This way you can keep the different Radiator versions and switch between them to upgrade/downgrade as required.
You can also set up your startup scripts to do the same thing.
regards
Hugh
On 07/01/2004, at 7:34 AM, Erich Zigler wrote:
What is the best/easiest/cleanest/supportable way to upgrade radiator?
Thank you.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. - CATool: Private Certificate Authority for Unix and Unix-like systems.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
