> 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.
Ahh, yes, this is what I was trying to figure out.
> 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?
I've got one unnamed session database, followed by SDB1 and SDB2. It seems
to be using the first one as the default, and thus working correctly.
Perhaps it uses the last unnamed one? (Maybe I should go look at the code
too)
--
Roy Hooper ([EMAIL PROTECTED])
Sr. Systems Administrator
Network Operations
Cyberus Online Inc, an eisa.com company
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
