On http://wiki.freeradius.org/index.php/FAQ, question 6.10 I read: <quote> With FreeRADIUS you can simply use: radiusd -C to check the configuration. [...] </quote> But when I try to do that: <code> # radiusd -C radiusd: invalid option -- C Usage: radiusd [-a acct_dir] [-d db_dir] [-l log_dir] [-i address] [-p port] [-AcfnsSvXxyz] </code> I'm using FreeRADIUS 1.1.6. G.L. -- www.aldu.net/~heruan giovanni.lovato@aldu.net
A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
<quote> With FreeRADIUS you can simply use:
radiusd -C
to check the configuration. [...]
gone
deprecated
So how could I check configuration before sighupping the process? I try a script called ``check-radiusd-config'' but it gives me: # check-radiusd-config Radius server configuration looks OK. also when configuration IS NOT OK! Any other new method or option to do that? G.L. -- www.aldu.net/~heruan giovanni.lovato@aldu.net
Giovanni Lovato wrote:
So how could I check configuration before sighupping the process? I try a script called ``check-radiusd-config'' but it gives me:
The preferred method is to have a test server. Generally you want a primary and secondary server anyways and often I will use the secondary to test minor changes since there is very little traffic there normally. Aside from that, I think you can change the port it listens on and start another process along side the production one. Then as long as you don't mess up the syntax when changing the port back, you should have your test. -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
participants (3)
-
A.L.M.Buxey@lboro.ac.uk -
Dennis Skinner -
Giovanni Lovato