> [major snippage]
> > Well, naturally I could run radiusd in blocking mode, but then what is the
> > purpose of running it under inetd at all? Why not just run it standalone,
> > if in blocking mode.
> Insurance against radiusd crashing, I guess.
I have the equivalent of a mini-inetd that we run things like RadiusD in.
It's a wrapper which is run at system startup and does nothing but
infinitely loop running RadiusD. Should RadiusD ever crash, it simply
restarts it with appropriate messages via email to the manager. The only
way to lose RadiusD completely would be if it got so upset that it managed
to not only kill its own image but also take the process down with it. In
OpenVMS, that's almost impossible. In any case, RadiusD (Livingston
version + my VMS port) has been so stable that it's never crashed since I
put it into place, about November/95.
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.