Some of the parts which did not suffer well in the translation
include Radius' tendency to want to fork() lots (which isn't
as speedy in VMS as it is in many Unix systems) as well as
the use of hardwired filenames.
Has anyone also done this? I would like to compare notes with
them to see if there are any loose ends I've missed.
There are a small number of subtle bugs in the Radius 1.16 code now on
Livingston which came up as part of the port; most are in the
declaration of variables and some improper casting. Does anyone
out there care?
Also: I have used the #ifdef __vms (which is the VMS-standard way
of #ifdef-ing for itself) and VMS_SYSUAF (which is my flag to say
"use the system authorization file instead of the text file for
usernames & passwords"). Should I be registering those with someone?
Other questions:
Has anyone written a Q&D utility to summarize the accounting records
which Radius generates?
jms
Joel M Snyder, 1404 East Lind Road, Tucson, AZ, 85719
Phone: +1 520 324 0494 (voice) +1 520 324 0495 (FAX)
jms@Opus1.COM http://www.opus1.com/jms Opus One
PLEASE NOTE: The useful parts of Arizona changed
from area code 602 to area code 520 on March 20, 1995.