While non-optimal, would a mutex lock around non threadsafe functions be a viable workaround? It at least allowed a program I've written to function safely ..
Penned by Alan DeKok on Mon, Feb 25, 2002 at 05:44:48PM -0500, we have: | [EMAIL PROTECTED] (Rainer Clasen) wrote: | > Even with the changes from the radiusd.c you sent me, this goto is still | > triggered. | | <sigh> I think it's the threading problems. The server still uses | a few functions which aren't thread-safe, and they should be made | thread safe. | | e.g. gmtime(),. etc. | | I've made a number of changes to the code in CVS. It should be | *more* thread-safe than what it is right now. I don't know if it's | perfect yet. I'll have to audit the rest of the code, and that can | take a while. | | Alan DeKok. | | - | List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Todd Fries .. [EMAIL PROTECTED] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
