From: "Serkan SUBASI" <firstname.lastname@example.org> Subject: [RadiusNT] RadiusNT Cache mechanism Date: Mon, 8 Jan 2001 01:15:48 +0200 Message-ID: <00b501c078ff$c537dca0$87b6d6c3@SSNBTEC>
Does radiusNT cache mechanism take care of queued accounting ODBC queries , for the concurrency concept
(for this case , ignore SNMP concurrency check and suppose that its disabled)
i.e. lets make a scenario
test1 user has a loginlimit 1 , and connected,
serverports show one test1 user at that time
and user disconnected after a time,
radius take the stop request , but there are some records in accounting ODBC queue, test1 users update serverports query started to
but before the query executed, test1 user trying to connect again, send his auth request to the same radiusNT server,
what will happen now ?
and apply this scenario with a loginlimit 2, what will happen ?
does RadiusNT take care of this condition or just SNMP concurrency check will solve the problem ?