Hey Alan, you suggested:
Fix is so that nothing is blocking the server.
Call me dump, but I have no idea what to look for. One idea: is ntlm_auth referred to as child? Maybe I sould write a wrapper and see how long execution of this "helper program" takes, or can I somehow log what program had which PID? Best, Jan Alan DeKok <aland@deployingradius.com> hat am 30. August 2010 um 22:22 geschrieben:
Jan Zacharias wrote:
I did more tests (now with two winXP clients and one OSX client),
the problem is still unsolved:
<shrug> The solution is still the same.
The strange thing: freeradius is started with the "no childs" option: freeradius 60384 0.0 0.4 11560 9240 4 S 11:57AM 0:49.13 /usr/local/sbin/radiusd -s
Well... something is inconsistent. The error messages you posted are produced *only* when the server has child threads.
So why does it complain about childs that take to long?!
For the same reason as before.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html