(RADIATOR) Global MySQL timeout ?

[Hugh Irvine]

Hello Ingvar -

This is correct. All modules that use a specific database employ a 
common connection.

regards

Hugh


On Tuesday, Sep 23, 2003, at 23:33 Australia/Melbourne, Ingvar 
Bjarnason wrote:

> Hi all,
>
>     It seems to me when Radiator connects to MySQL that if one handler 
> has
> trouble connecting to the db (locked table etc) and times out thereby
> flagging the db down for a set timeout period, all other handlers, 
> authby´s
> og authlogs using the same db will flag the db down as well.   It´s 
> like
> there is a global timeout.    Anyone else seen this happen ?    I'm 
> still
> looking into this btw. so I may be wrong.    If true this has the
> unfortunate side effect that if you for example temporarily lock a 
> table a
> specific handler is using the whole db is marked offline.
>
>     Best regards,
>                              Ingvar
>
>
> Ingvar Bjarnason
> Data division
> Iceland Telecom
>
> ===
> 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, 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.