What will be reloaded by freeradius server on received SIGHUP signal?

[Alan DeKok]

On Mar 30, 2018, at 11:58 AM, work vlpl <thework.vlpl at gmail.com> wrote:
> I want to know what will be reloaded by freeradius server on received
> SIGHUP signal.

  Some modules, and the virtual servers.

> I found this message in archives
> http://lists.freeradius.org/pipermail/freeradius-users/2010-November/050062.html
> 
> Is it still true?

  Yes.

> Also I tried rename certificates filepath  in eap to wrong value.
> After kill -HUP radiusd not stop. But in debug output radiusd print
> this
> 
> Ready to process requests
> Received HUP signal
> HUP - Re-reading configuration files
> including configuration file /usr/local/etc/raddb/radiusd.conf
> including configuration file /usr/local/etc/raddb/proxy.conf
> including configuration file /usr/local/etc/raddb/clients.conf
> including files in directory /usr/local/etc/raddb/mods-enabled/
> including configuration file /usr/local/etc/raddb/mods-enabled/eap
> including configuration file /usr/local/etc/raddb/mods-enabled/detail.log
> including configuration file /usr/local/etc/raddb/mods-enabled/ntlm_auth
> ...
> 
> So radiusd report what it reread eap config. That probably means what
> radiusd know about changed in eap module.

  No.  It checks the configuration files, but it doesn't reload the EAP module.

  If it reloads a module on HUP, that module name is printed in the debug output.

  Alan DeKok.