Hi! We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation. Thanks! JB
Hi,
We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation.
works here - but be aware that the configs are not compatible. you can just dump 2.x config onto a 3.x server (or vice-versa) alan
On 12/12/13 12:20, A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation.
works here - but be aware that the configs are not compatible. you can just dump 2.x config onto a 3.x server (or vice-versa)
One suggestions - we broke our configs out into a "common" and "main" file, using $INCLUDE in the latter. You can then tweak the "common" slightly, leaving the main config alone.
Hi! Thanks a lot for the confirmations and suggestions! JB
Hi,
We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation.
works here - but be aware that the configs are not compatible. you can just dump 2.x config onto a 3.x server (or vice-versa)
One suggestions - we broke our configs out into a "common" and "main" file, using $INCLUDE in the latter.
You can then tweak the "common" slightly, leaving the main config alone.
Remember to have different directories for the dictionaries . Had fun at one point where /usr/share/freeradius had v2 dictionaries and I was running with V3 code Rgds A Sent from my iPhone
On 12 Dec 2013, at 13:11, JB <list.freeradius@me.com> wrote:
Hi!
Thanks a lot for the confirmations and suggestions!
JB
Hi,
We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation.
works here - but be aware that the configs are not compatible. you can just dump 2.x config onto a 3.x server (or vice-versa)
One suggestions - we broke our configs out into a "common" and "main" file, using $INCLUDE in the latter.
You can then tweak the "common" slightly, leaving the main config alone.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 12/12/13 11:38, JB wrote:
Hi!
We would like to start testing 3.0 but don't want to replace our 2.x testing environment just yet. Before we botch up our installation we wanted to make sure if ".configure --prefix=/my/dir" suffices to completely isolate the 3.0 installation.
Yes. I've done this, and it worked fine.
JB wrote Before we botch up our installation we wanted to make sure if ".configure -- prefix=/my/dir" suffices to completely isolate the 3.0 installation.
We actually manage to run them out of the same directory. The nuance is you have to set the dictionary path on the commandline for the 3.0 instances with -D and deal with a few collisions if you are using the stock directories/files.
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Alex Sharaz -
Brian Julin -
JB -
Phil Mayers