[RADIATOR] radiator exists on ClientSQL timeout

[Heikki Vatiainen]

On 06/16/2011 11:00 AM, Heikki Vatiainen wrote:

> I took a look at some possibilities: what do you think about an option
> that instructs Radiator to close the database connection after the
> clientlist update? Then there would not be problems with firewall
> mangling the connection. I have not discussed the option here yet, but
> this is something I have thought about.

Based on discussion on this list and other input that I received,
patches for 4.8 now has this:

2011-06-18 ClientListSQL.pm sql.cfg
    Improvements to ClientListSQL to support DisconnectAfterQuery,
    which will cause disconnection from the SQL database after
    each query. This can be helpful in cases where firewalls etc
    close connections that have been idle for a long time.

Configure it like this:

<ClientListSQL>
  # Existing configuration
  DisconnectAfterQuery
</ClientListSQL>

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.