On Thu, 14 Oct 1999, Ric O'Connell wrote:
> Hello all,
>
> We have Radiator authenticating to our Oracle SQL database. I have a schema
> per realm, so I am wondering how Radius's AuthbySQL module will handle this.
> Is it going to open a connection to one database, then close it, and then
> open a connection to the other database?
>
No - Radiator will connect to the database at startup and keep the connection
open forever. If the connection goes away, Radiator will try to reopen it, or
move to an alternate database if one (or more) is defined in the configuration
file.
> DBI-->Connect statements are costly and slow, and I'd like to keep the
> Database pointer open as long as Radiator is running. Will it open a pointer
> per realm, or is the SQL pointer a global varialble? I've poked around a bit
> in AuthSQL.pm and it looks like you open the database in "initialize" which
> is called once per instance and not "new" which is called once per realm. Is
> this right?
>
The database connections are opened in SqlDb.pm in the routine "reconnect".
hth
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.
