Hi... on my delayed reading of the list I found this:
El 18 Apr 2001, a las 9:45, Hugh Irvine escribi�:
>
> Hello Andy -
>
> The session database will be accessed by both authentication (to delete and
> to check limits) and accounting (to insert and delete).
>
<SNIP>
So... I have different instances of Radiator for accounting and
authentication, then BOTH have to have the <SessionDatabase> clause? And
should they be identical?
On re-reading the "Performance and Tunning" section in the manual
(http://www.open.com.au/radiator/ref.html#pgfId=406539), I find a good
list of hints, but most of them are sometimes not very usefull when you
DO have to do some strange things... anyway, since I saw it many times in
the list, the separation between an Authentication server and an
Accounting server in different instances even when it is in the same
machine, seems to be a no-lose proposition, since you are losing no
functionality at all (I think) and you don't have to buy extra hardware
(it's easy to say "see, boss, I need 4 or 5 more Sun Netras T1 to improve
radius speed" only to hear him say "gee, why don't you do it with that
Sparc I that no one is using now?").
Since I see this so often said in the list, it might get a subsection
with some configuration tips for this, like, "you have to put this kind
of sections on the auth config, those sections in the acct config and
this bunch in both... maybe you should use "Include common.cfg" for these
last ones...
Put it in the wishlist for the next release (2.18.2? 2.19? please don't
do anything like naming it "Radiator 20" -� la Solaris- or "Radiator
2001" or "Radiator NE (Nonsense Edition)" -� la MS- :-)
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
