I've done a little digging but I can't find the answer. Radiusd starts fine in all circumstances. It will authenticate only one session, and then the CPU will spike to 100% and radtest will just run through it's 10 cycles and timeout.
This happens when I run radiusd in any of the following ways: Radiusd Radiusd -f Radiusd -fxx Radiusd -fxxy Radiusd -fxxyz It runs just fine when I run radiusd with the -s flag in any of the top examples. Any one know why this might be happening? FYI: If I run -fxx, I get no debugging information from the server at all, so unfortunately it's not going to be any help :( - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
