Danial wrote: > Well, I've now monitored an "Exiting normally" event using ktrace:
That helps. > 655 radiusd RET write 84/0x54 > 655 radiusd CALL close(0xa) > 655 radiusd RET close 0 > 655 radiusd PSIG SIGSEGV SIG_DFL Ugh. > It seems I can semi-reliably replicate this scenario. When I force this > radius server to become the primary, it exits after a few hours. If you can, see doc/bugs. Re-build with debugging symbols, run it under "gdb", and we should be able to get a backtrace containing the exact line which has a problem. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
