> Aha! Someone else with the same sort of problem. I have been meaning
> to write to the list and ask for advice also.
>
> > I tried upgrading to 2.4.20, and it still happens...randomly, it seems
> > (it happened about every 20 minutes up until noon yesterday, and hasn't
> > yet today), though I noticed another symptom...apparently some accounting
> > entries are getting corrupted (replaced with garbage). It hasn't
> > happened yet today, but did happen yesterday, so I think they may be
> > connected.
>
> I am attempting to upgrade to 2.4.20. The radiusd will not even start.
> Running it in standalone mode, not from inetd (at the moment). Our specs:
> Merit 2.4.20, BSDI 2.0/486, No shadow.h. No other patches or modifications
> except the one below.
[...]
> The compiled radiusd+LAS will not even start; it says "segmentation fault"
> and dies. An inspection of the radius.debug file (generated by -x -x -x -x)
> tells me nothing. The last few lines are:
Hmm...doesn't seem like the same problem. My radiusd (not using LAS)
starts just fine, even handles authentication and accounting requests
(though it misses some accounting when it crashes), but at random times
will segfault and die.
// Matt Zimmerman Chief of System Management NetRail, Inc.
// mdz@netrail.net sales@netrail.net
// (703) 524-4800 [voice] (703) 524-4802 [data] (703) 534-5033 [fax]