How to disable threads in 2.1.7

[Craig Campbell]

>From the man page for radiusd, the -s option specifies,
"Some systems have issues with threading, however, so  running
              in  "single server" mode may help to address those issues."

I cannot help but wonder if in fact others have been seeing this, and just 
opted for -s and less efficiency.

At this point all the (troubled) server receives are accounting packets   It 
then relays these packets to two (2) other radius servers, and processed 
them according to acct_users, which in turn runs a script for Stop packets.

Thus far, only running an external script has been identified (thanks Alan) 
as creating child processes of radiusd.

I really would LOVE for this to be a configuration error on my part, but so 
far I cannot locate one.

Thanks,
-craig
----- Original Message ----- 
From: "Phil Mayers" <p.mayers at imperial.ac.uk>
To: "FreeRadius users mailing list" <freeradius-users at lists.freeradius.org>
Sent: Friday, October 16, 2009 8:52 AM
Subject: Re: How to disable threads in 2.1.7


> Craig Campbell wrote:
>> I was hoping to build a version that could fork children, but not spawn 
>> threads.
>
> Not possible.
>
> You could run lots of copies with a single thread bound to different UDP 
> ports, and load-balance them somehow.
>
>> I cannot explain why apparently no one else is seeing the issue I am 
>> chasing.  As far as I can tell, my configuration is quite basic.
>
> The fact that it's not happening for anyone else would tend to indicate 
> it's specific to your system. We fork processes on accounting in some of 
> our virtual servers, and this doesn't happen.
> -
> List info/subscribe/unsubscribe? See 
> http://www.freeradius.org/list/users.html
>
> __________ Information from ESET Smart Security, version of virus 
> signature database 4514 (20091016) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
> 


__________ Information from ESET Smart Security, version of virus signature database 4514 (20091016) __________

The message was checked by ESET Smart Security.

http://www.eset.com