Rohaizam Abu Bakar wrote:
> How can we possible do to ensure only when sql1 down.. then the accounting
> will be sent to sql2..??
You might try a different approach:
- store accounting in "detail" files (man rlm_detail)
- run radsqlrelay to send accounting in the database (get it from a
CVS snapshot)
Even if the SQL server is down for a day, radsqlrelay will buffer the
accounting packets and send them later.
The advantages:
- all accounting go in a single database (it's easier to check
simultaneous login)
- even under high load radsqlrelay still sends accounting requests
according to the SQL server's capabilities
- you won't have a lot of outstanding requests on the RADIUS sever
when the SQL server is slow
--
Nicolas Baradakis
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
