There is no way in Radiator itself to go back to using database A when it comes back.
Note that you could just define two seperate AuthBy SQL clauses, but I don't know if this will work for you.
Most operators tend to use a single database on some sort of high-availability hardware.
regards
Hugh
On Monday, August 19, 2002, at 05:19 PM, Achint Saxena wrote:
Hi,--
Just a quick question. I've got a pretty straightforward configuration here. I have my radius servers pointed to 2 SQL databases.
When database A goes down, Radiator switches over to database B. This works fine.
My question is, is there anyway to go back to database A when it returns to operational? The current behaviour is to stay put at database B until it goes down too. FailureBackoffTime doesnt work in this way.
Any ideas.
Thanks.
Achint.
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
