> There's -c option for radiusd. It will read the configuration and
> checks what it can. It does not, for example, attempt to connect to
> SQL databases, so it will not catch those types of problems.
it does appear to do RADSEC connections though. maybe SQL connectivity should
be part of the test (or an option with another flag?)
> There's actually work ongoing to enhance configuration checking.
> Currently the output from -c is more for human consumption, so the
> exit code, for example, does not reflect the check results. We are
> looking at returning different exit codes depending of level of
> problem (warning, error) from -c run.
yes, interesting timing on this query since I've been recently in contact
with OSC over this feature :)
> What you could do now is to wrap radiusd -c invocation with a script
> that greps errors and warnings and then returns non-zero exit code.
...if you get output ;-)
radiator mailing list