Edgard Castro <[EMAIL PROTECTED]> wrote: > Oh, sorry. Misunderstood that one. Yeah definitely, this is the > configuration of thread poool that I have: > > start_servers = 64 > max_servers = 512 > min_spare_servers = 15 > max_spare_servers = 30 > > Looks reasonable, right?
Yes. That's OK. > I found that reference on the list: > > http://lists.cistron.nl/pipermail/freeradius-users/2001-June/001027.html Hmm... that patch *wasn't* applied to the PostgreSQL module. If it does fix the problem, I'd like to know. > But not "freeing" something sound kinda frightening to me, plus I dont know > if that would introduce any inconsistency nor help with the problem. That does sound bad. But if the patch doesn't crash, it may be useful to apply it. > radiusd -X shows a funky behavior. If I increase over 25 the number of > connections, the radiusd is able to register/answer just ONE request and > them simply stalls waiting for "the next request". Stalls *where*? Knowing where it stalls is the key to solving the problem. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
