Clone Function Called with each Authentication Request

Boian Jordanov bjordanov at
Fri Oct 10 09:38:10 CEST 2008

See the comments below.

Best Regards,
Boian Jordanov
Orbitel - Next Generation Telecom
tel. +359 2 4004 723
tel. +359 2 4004 002

On Oct 10, 2008, at 9:08 AM, David D wrote:

> Hi,
> I'm testing an Authentication script and it's working great.
> I need to optimize the performance and move some data stored in  
> files into
> memory.
> To accomplish this, we planned on placing the routine to read the  
> data into
> memory in the clone
> function, so it would load once.
>> From reading the documentation and the posts I could find.
> It's my understanding that the CLONE function will only be called  
> once for
> each new thread created.

Correct. This a place in which you should do per thread initialization  
of some variables like database connections etc.

> In my testing I've noticed that the CLONE function get's called for  
> each
> Authentication request, so it appears
> the thread is initialized for each call, even though I see it load  
> up all 32
> threads when radiusd initializes.

There is something wrong. If you can share with me your script  
probably i can help.

> The debug output shows all 32 threads calling the clone function and  
> then it
> shows the clone function called again
> when an authentication request comes in.
> Any ideas on what I could check or change?
> radius0-dev:/etc/raddb # radiusd -v
> radiusd: FreeRADIUS Version 1.1.3, for host x86_64-unknown-linux- 
> gnu, built
> on May  8 2007 at 19:12:20

Please upgrade your freeradius to more newer version.

More information about the Freeradius-Devel mailing list