10.3. Using inetd Previous topic Parent topic Child topic Next topic

If you do not wish to use restartWrapper or init, you can instead arrange for the Unix inetd(1) super server to start radiusd the first time it is required (and to restart it if it stops unexpectedly). In order to do this, you must add a new line to the inetd configuration file (usually /etc/inetd.conf). You must also ensure that the radius port number you wish to use is configured into the /etc/services file. You must also ensure that Radiator is configured to run in the foreground with the Foreground parameter or the -foreground argument. For more information, see Section 3.7.1. Foreground.
The inetd line you add will look something like this (the line has been wrapped due to its length in this example):
# Start Radiator on demand
radius dgram udp wait root /bin/radiusd radiusd 
      -config_file /etc/radius.cfg
After changing /etc/inetd.conf, you will need to tell inetd to reread its configuration file by sending it a HUP signal with something like
kill -HUP pid-of-inetd
Whenever a radius request is received and radiusd is not already running, inetd will automatically start radiusd. If radiusd stops some time later, inetd will restart it when the next request arrives. For more details on using and configuring inetd, consult your Unix vendor's documentation.
Make sure that Radiator is running in “foreground” mode, either with -foreground in the command line arguments, or with Foreground the configuration file.