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 > radiusd ? Meaning can I safely run another instance that points to > fresh config file and have it run on an alternate port ? Yes, this is possible. Just see that log and pid file names etc. do not overlap. Read-only files, such as dictionary, can of course be shared. With careful configuration you should not have problems. One common case is to have a separate authentication and accounting instance. So besides testing, multiple instances can be run for separate functionality and/or load balancing purposes too. > I'd like to > do some testing for a development wireless domain and minimize the > impact on any current production use of radiator and would prefer not > to have to do it on another box IF I can do so with no impact to > production use. I see no problem doing this. One option might be to run the instances under different uids and groups. If the test instance tries to e.g., write to wrong log file, the file permissions should stop it causing any actual harm. Thanks! Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
