Hello Wesley -
If the SQL database access times out, Radiator by default will wait 10 minutes before trying again.
You can adjust the Timeout and FailureBackoffTime parameters in the AuthBy SQL clause.
See sections 6.28.4 and 6.28.5 in the Radiator 3.6 reference manual.
regards
Hugh
On Sunday, Jul 20, 2003, at 19:11 Australia/Melbourne, Wesley Hof wrote:
Hi,
I'm using radiator v1.91, when a customer try's an authentication it first
checks a few berkeley files. If the user isn't found inside the berkeley
radiator querys an oracle db.
Now, because of the large numbers of querys on the oracle db (other
applications) it sometimes happens that a query from radiator times out, i
see that in the radiator logs. The strage thing is, when a sql query to
the oracladb timeouts, my radiator freezes/stoppes and I need to restart
it.
Is there somekind of reasen?
Thanks in advance, Wesley Hof.
System Administrator. Uninet International NV/Planet Internet. Tel: +32 (0)3/275.15.41
-- uniX, the source is out there! === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
