(RADIATOR) Taking too long.

[Hugh Irvine]

Hello Griff -

As always, a trace 4 showing what is going on is what is required.

For sub-second timer resolution you should use the LogMicroseconds parameter 
with the Time::HiRes module from CPAN.

You may find that you will have to have multiple Radiator hosts with some 
form of load balancing in front, and/or seperate authentication and 
accounting instances of Radiator on each host.

hth

Hugh


On Friday 14 September 2001 09:16, Griff Hamlin, III wrote:
> Hello,
>
> I am using an SQL database for authentication, Accounting, and session
> database. I also am using snmpget to keep my online database consistent.
> I find that when the snmpget takes a little too long, radius gets behind
> and will never catch up, effectively denying all users as their
> computers time out although eventually they do get authenticated on my
> end. I thought about trying to fork processes, but is there no way to
> limit the number of running processes that spawn off? Does anyone have
> any experience with this type of problem and/or how to solve it?
>
> Griff Hamlin, III
>
> ===
> 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.

-- 
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.