> Tonight I experienced a lockup of radisud (v2.0). Once it failed, all
> logins failed on all portmasters. The only way I found to fix it was to
> replace the executable with the original that I had saved in another
> directory. Has anyone had this problem, or know what might have caused it?
> I have checked the log files and I don't see any signs of a problem at the
> time of the failure.
Please be more specific. What do you mean by "lockup"? Did radiusd core
dump or just stop responding?
If you have *ANY* Ascend equipment using the same radiusd as your
Livingston equipment, you will need to apply a patch to the source and
recompile.
Also, you mentioned replacing the executable. Radius 2.0's dictionary has
new/different values than before. There are some changes you need to make
to the /etc/raddb/users file to use Radius 2.0 effectively.
Chad Scott | chad@txdirect.net
Systems Administrator | Voice 210-308-9800 x206
Internet Direct, Incorporated | FAX 210-308-9240
---------------------------------------------------------
Finger chad@txdirect.net for PGP Public Key