(RADIATOR) Timeout in RADONLINE

[Hugh Irvine]

Hello Andreas -

The only solution currently is to run a cron job outside of Radiator that 
goes around and checks the NAS connections and keeps the RADONLINE table in 
sync.

regards

Hugh


On Tue, 12 Feb 2002 19:56, Andreas Häggander wrote:
> Hi !
>
> We are using Radiator 2.19 with Nortels BSN Shatsa 5000.
>
> Sometimes we miss a stoprecord or something happens with the BSN, the user
> tries to reconnect, but the user is still in the RADONLINE database.
>
> How can we solve this ? Are there any timeouts or something ?
>
>
> <SessionDatabase SQL>
>           Identifier      SQLSDB
>           DBSource        dbi:mysql:radius:localhost
>           DBUsername      xxxxxxxx
>           DBAuth          xxxxxxx
> </SessionDatabase>
>
> Cheers
>
> /andreas
>
>
> ===
> 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.