Graeme Hinchliffe <[EMAIL PROTECTED]> wrote: > I have now tried the unmodified code and exactly the same behaviour > occurs. The number of threads steadily increases, default started > with 11 and over the space of 30 minutes it is up to 19
There's not much I can say. If no one else can reproduce the problem, then it's extremely difficult to track down. You can try running: ./radiusd -xxx which will print out full debugging information, AND use threads. Re-direct it to a *large* disk, and root through the logs, looking for 'unresponsive child'. Look backwards from that point, for the original request, and how it was processed. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
