"RATI,SIDDU (HP-Cupertino,ex1)" <[EMAIL PROTECTED]> wrote: > The problem is occurring under load only, and is not occurring all the time. > I also suspect, this could be because of race condition in the server as of > at present the server is not multithreaded. Multithreading may resolve this > problem.
Then why not run it with threads? That's the default! For these sorts of issues, do NOT disable threads. The multi-process version of the server does NOT work well, if at all. Note that the server code reading the packets is NOT multi-threaded. This is because it does minimal work to sanity check the packet. All of the CPU intensive work is then farmed out to a thread. So each new request is handled by a different thread. The server core takes care of creating new threads, and assigning requests to waiting threads. There should be no locking or race problems here, because the core is designed to NOT need locks when giving requests to threads. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
