Logging the debug output

Alan DeKok aland at deployingradius.com
Thu Nov 10 00:05:16 CET 2016

On Nov 9, 2016, at 5:35 PM, Brett Randall <brett.randall at gmail.com> wrote:
> I have an ongoing issue with a FreeRADIUS third-party module that is very
> intermittent (only shows up at a random time each day).

  a) tell them to submit the module so we can include it in the distribution, and support it officially

  b) ask them to fix their module.

> In the past,
> running FreeRADIUS in debug mode has been very helpful, but I don't like
> leaving it running from a command line indefinitely. Is there a config
> setting that allows me to log the same output that that the debug mode
> produces to a file that I can then go through at a later stage? I realise
> this will impact performance and consume space...

$ radiusd -X  > file

  That's the simplest thing.

  And in general, we discourage third-party modules.  They're mostly broken and/or badly written.

  Alan DeKok.

More information about the Freeradius-Users mailing list