> YEP! Bummer! It blew the shit out of my system too! My system worked
> fine for many months until I upgraded to Linux 2.0.30 (from 2.0.29). Then
> it blew every couple of hours. The solution is Radius 2.0.1. I have had
> it running for a couple of weeks and my monitoring script, the one that
> restarts it upon failure, is also set to email me on each restart of
> Radius: I have been running clean since the upgrade (no restarts). The
> primary symptom for this (according to Livingston's voice Tech Support) is
> an entry in the syslog file: died on signal 100. What it is trying to do
> is kill off it's orphaned children. The parent mistakes itself for a
> child and recklessly kills itself!
>
> Radius 2.0.1 is the answer.
Thak seems to be the answer. I've got 2.0.1 compiled, and now that I'm
back in the office, I'll give it a go.
Thanks to everyone for the swift answers!
--Mark