Great, thanks to everyone who made suggestions, I'm going to go ahead and implement according to Alan's suggestion because of the amount of seperation that it gives and it seems the best way of acheiving this. One other point, if we are using a an sql backend then the radiusd process would never have to be restarted as well right?


Alan DeKok wrote:

The benefit with this approach is that no matter what the customer
does to the database, it's *impossible* for them to affect any other
customer.






- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to