Hello Aaron -
On Fri, 26 Nov 1999, Aaron Holtz wrote:
> Guilherme,
>
> I've brought this issue up before, but in regards to moving from a
> backup sql server back to the primary. But I think the same principals
> hold true between your setup and mine. The rule is that once radiator
> moves to a backup/secondary means of authentication, that it will only
> move on (or back to the original) if the secondary method times out or
> stops responding. I had suggested a timer that locks down the "bad" means
> of authentication when a backup is used. After the timer expires the
> primary means should be retried to see if it is responding - then the
> whole process starts over or the secondary is continued to be used
> and the timer is reset. I'm not sure how feasible this idea is, but
> it sure would make using backup means of authentication much easier to
> use. Often times my primary means of authentication is down for a few
> minutes during the off hours for cleanup of the database - using a backup
> would be great during that time. But I don't want that backup used for
> too long - hence my reason for a timer to lock out the primary method.
>
We're considering it for the next release.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
