Re: radius 2.0 dies with signal 100

Zak Wolfinger (zak@MichianaToday.com)
Thu, 10 Apr 1997 08:18:46 -0500

Had the same problem here. Turns out that we had too many users in our
user file to run Radius without using the builddbm util and compiling the
userlist into a database for faster searches. Hope that helps!

Zak Wolfinger - zak@michianatoday.com
Systems Administrator - CyberLink, Inc.
(219) 235-1400 (219) 674-8279
FAX (219) 235-1599

----------
> From: Don Lewis <don@erc.jscc.cc.tn.us>
> To: portmaster-users@livingston.com
> Subject: radius 2.0 dies with signal 100
> Date: Wednesday, April 09, 1997 10:09 PM
>
>
> I've tried 3 different Linux 1.2.13 boxes with the radiusd 2.0 binary
from
> Livingston and they all die with signal 100 as soon as traffic hits them.
> I'm running lots of pm2's and pm3's with OS 3.5> and radius1.16 never
> falters. (could it be a trick and I need to reboot all portmasters at
once
> then start radius2.0)
>
> Running radius 2.0 in debug shows nothing but the tickets before the
fatal
> message. Moving to a different version of Linux is too big of a chore now
to
> tackle but I do need radius 2.0.
>
> I've recompiled Linux with various settings with no luck. I've seen
> this signal 100 problem mentioned in questions re: radius2.0 but no
answers
> were posted that I can find.
>
> Also, I tried to compile the radius 2.0 src on both RS6000 and Linux and
> both compiles fail because of no rule to make sdacmvls.h and I've given
> up trying to find docs on radiud source compiles. Maybe if I can compile
on
> my box radius 2.0 will run ok. Thanks for your help.
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Don Lewis Jackson, Tennessee
> dlewis@erc.jscc.cc.tn.us
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =