We noticed a ***MAJOR*** problem with radius server and logging accounting information to the SQL server.
The problem is, for whatever reason, if the SQL database server dies and when the database server is restarted and come back online, the radius server is still unable to continue to log new accounting information to it, ie it seems the connection context is obtained during radius server starts up, and it maintains it throughout the entire life of the radius server and never atttempt to re-new it when it becomes stale. This will post a MAJOR problem especially when the radius server goes across the network to log accounting information to a SQL server, ie the external server and network can fail and it will definitely fail at some point in time. We have tested this behaviour using unixODBC/freetds connection to Microsoft SQL server. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
