Hi Roy -
On Mon, 29 Nov 1999, Roy Hooper wrote:
> Thanks! That worked well.
>
Good.
> Is there any way to just discard instead of using two (or 3) session
> databases?
>
No, not really, as you need the first one as a place-holder in any case. Its
always the first one that is used by default (** see comments below **), and the
second (and third...) can be referenced via the Identifier and used for other
purposes.
> What would happen if I told it to use a different SessionDatabase that I had
> not previously defined? :)
>
You would probably just fill up your log files quicker with complaints about
not being able to access that session database.
Note however that you can specify an internal session database, just like the
others, and as it runs entirely in memory it will be fast and won't leave
anything lying around.
# define an internal session database as the first default
<SessionDatabase INTERNAL>
Identifier SDB1
</SessionDatabase>
Actually, I have just been looking at the code, and it says that the *last*
session database defined will be the default. Which way did you set up your
configuration? And does it work as you would expect?
thanks
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.
