Freeradius 1.1.1: 'sqlippools' concurrency problems

[Robles Rodriguez,Alejandro]

"Alan DeKok" <aland at nitros9.org> wrote:
>  A simple solution would be to go to the bottom of rlm_sqlippool.c,
>and change it from RLM_TYPE_THREAD_SAFE to RLM_TYPE_THREAD_UNSAFE.
>Then re-compile & re-install.

  That would be the case if I only had one single radiusd running, however as
already mentioned this solution encompasses a number of radius servers each with its
own mysql server adn the same storage (NDB cluster) behind the scenes i.e. virtually
sharing data storage.

  By implementing the suggestion (which by the way didn't know
it was possible so thanks for the tip) I would only solve it for one radius server
(at the expense of a lower performance) but not wen several radius servers are at play.