Re: Start Freeradius at boot
did you install FreeRADIUS via yum and a repository or from source?
Downloaded freeradius-server-2.1.7.tar.gz, extracted to home directory, and then ./configure, make, make install.
if from the repsository you should have a selectable service with eg the standard Fedora system startup tools - maybe they've decided to call it 'freeradius' or 'freeradius2' rather than radiusd?
There is a "Startup Applications" where I can add programs, but it doesn't start them until you log on to the machine and this doesn't work unless you log into the gui as root.
if from source, then the install part (make install) wont handle your OS directory - you'll need to copy the script (and maybe edit it according to install path choices made) from the contrib directory eg redhat/rc.radiusd-redhat to the correct place - /etc/init.d/ i'd note now that its not just the startup item - theres also a logrotate script which ties into the system logrotate cron stuff to ensure that freeradius logs (eg /var/log/radius/ get rotated when needed - eg each day for 90 days retention) alan
hi, note sure why you are reversing the email conversation tags, however you installed from source so, in the source directory (where you ran ./configure) there is a redhat directory. in that directory is an rc. file - that needs to be copied into the /etc/init.d eg cp rc.whatever /etc/init.d/radiusd then use the appropriate tool to ensure this starts by default (I use chkconfig - from the old school) but Fedora does have system admin tools to ensure that daemons start up when the system starts up - i know..i've had to use their tool just once or twice. since I cant use such tools att he end of a 14.4 baud dual up to a comms centre across the pond, i use SSH with eg chkconfig extensively) you'll want to then check everything is A OKAY by eg service radiusd start service radiusd status service rediusd restart the first thing will test it can be started with the script. as i said before the script was written some time back and some directories might not exist and some permissions might be wrong! if the script fails or 'status' test fails then check the /var/log/radius/radiusd.log to see maybe reasons why. once its all running fine, then the service will restart fine upon reboot. even if the system is a VMWare instance on a Max OSX server - doesnt matter what its on, the basics will always be the same with that distro. alan
The quoting in this thread is so confused I'm not going to try and unravel it. The Sytem -> Preferences -> Startup Applications menu item is only for desktop applications running in a session. That is quite a bit different than system services, sometimes called daemons. Typically the radius service is installed under the name radiusd following the convention that daemons have a "d" appended to them. That means you're trying to control a system service not a session based desktop application. This is done at the command prompt level with chkconfig or via a gui with system-config-services. You might have looked at: http://wiki.freeradius.org/Red_Hat_FAQ#How_do_I_start_and_stop_the_FreeRADIU... If you build from source and you don't know what a System V Initscript is then the algorithm is: 1) Stop 2) Install the pre-built package with all this stuff already figured out, tested, and done for you so you don't have to learn how to build from source *and* integrate with the OS, all the while making a lot of learning curve mistakes. Installing pre-built packages typically takes 1 minute of your time. Wasn't that easier? Fedora, RHEL, and CentOS all have current packages available. See http://wiki.freeradius.org/Red_Hat_FAQ -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
participants (3)
-
Alan Buxey -
John Dennis -
Paul.Blalock＠gmail.com