Guys, Thanks for the tips on doing this. I am putting together some
notes/details on the process and will get back if I have any other
questions.
-john
At 11:12 PM +0200 1/11/12, Heikki Vatiainen wrote:
>On 01/11/2012 09:46 PM, John Goubeaux wrote:
>
>> I have a basic "best practices" question
Hello John -
An alternative approach that I always use is to keep all versions of Radiator
in separate source directories, and run radiusd from the corresponding source
directory when testing and in production.
Ie. here is my source repository:
TiTi:Radiator hugh$ pwd
/Local/src/Radiator
Ti
On 01/11/2012 09:46 PM, John Goubeaux wrote:
> I have a basic "best practices" question on how I might best run a
> separate "development" ver of radiator for testing without impacting
> a production instance on my network.
> Can I, and should I do this on the same host running the production
Hello folks,
I have a basic "best practices" question on how I might best run a
separate "development" ver of radiator for testing without impacting
a production instance on my network.
Can I, and should I do this on the same host running the production
radiusd ? Meaning can I safely run anot