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
