(RADIATOR) practical limit of session database

[Hugh Irvine]

Hello Shan -

There is no particular limit to the number of entries in the session 
database. Your database should be able to handle many times more than 
10k records.

However, you are not correct when you say that Radiator updates the 
session database every 30 seconds. The session database is maintained 
primarily by radius accounting records from your NAS equipment. An 
accounting start will insert a record and an accounting stop will 
delete a record. If your NAS equipement is configured for periodic 
accounting updates, then those too will be used to maintain the session 
database.

regards

Hugh


On Tuesday, Apr 15, 2003, at 23:05 Australia/Melbourne, S H A N wrote:

> hi,
> 	my scenario is: i want to manage session database in a mysql table. 
> the point is to findout at any particular time a user is logged on 
> using what kind of "realm" (out of a few out there).
>
> 	my question is: what is the practical limit of a session database? am 
> i correct radiator updates it every 30sec? can it manage 10k+ enteries 
> at any one point of time? any experiences?
>
> rgds,
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.