Paul Hampson wrote: > > From: Nick Davis > > Sent: Wednesday, 1 October 2003 7:48 AM > > > One thing to note, when installing the deb files with dpkg -i, it > > will try to start the freeradius daemon. That failed because all > > of the modules that I removed were still defined in radius.conf. > > Interesting point... I might have to go fix it so that failing to > start the server doesn't cause installation failure... To my mind > server start failure is probably not so bad 'cause I suspect an > unconfigured RADIUS server would not be a pleasant thing to have > running.
As an other possibility you might call check-radiusd-config in the debian init.d script before starting the serveur. The init.d script of Apache (for example) do that. It could be wise to call check-radiusd-config too before doing a reload. If radiusd.conf is broken we don't stop a already running server. Looking at the source of check-radiusd-config I think it doesn't proceed properly, or to be more accurate, it doesn't do what I expect it to do. It should _only_ test the config, but it launch the whole server on port 32768 (including instantiating modules, opening db connexions, etc.) and kill it 2 sec later. I think FreeRADIUS should provide a -t option (like Apache) to test its configuration file. It's a trivial thing to do. I'm going to do it very soon (so it may go in 0.9.2) and post a patch on the -devel mailing list. -- Nicolas Baradakis - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
