Serializing database requests
Alan DeKok
aland at ox.org
Thu Sep 22 20:32:46 CEST 2005
Mike Chamberlain <mikeachamberlain at gmail.com> wrote:
> But the authorize procedure
> takes longer to process than the stop accounting procedure, meaning
> that the stop procedure completes before the authorize. This means
> that in effect the two messages get processed back to front. In our
> scenario this leaves a call open in the database that will never be
> closed.
>
> How do other people cope with this?
Post-processing the logs, and looking for these cases.
Or, delayed logging data to the SQL database. i.e. in the CVS head,
there's an "rlm_sql_log" module that logs SQL queries to a file. You
can later post-process the logs.
> Is there some way of forcing FreeRadius to serialize requests from
> the same username so it won't issue a new one until it has received
> a response for an existing one?
Not really.
Alan DeKok.
More information about the Freeradius-Users
mailing list