Hi Neil,
The reconfiguration of each Kea server is triggered by the SIGHUP
signal. The reload command sends the SIGHUP signal to the servers that
are enabled in the keactrl configuration file and are currently running.
When a server receives the SIGHUP signal it re-reads its configuration
file and, if the new configuration is valid, uses the new configuration
{code}
$ keactrl reload
INFO/keactrl: Reloading kea-dhcp4...
INFO/keactrl: Reloading kea-dhcp6...
INFO/keactrl: Reloading kea-dhcp-ddns...
{code}
El 14/09/17 a las 12:45, Thomas Markwalder escribió:
On 9/14/17 11:35 AM, Neil Briscoe wrote:
Thanks for the speedy reply Thomas.
Is “kill –SIGHUP <pid for kea>” the same as “service kea-dhcp4-server restart”
or is this slightly different?
Thanks,
Neil Briscoe | e. [email protected] | t. +44 7793 056923
<tel:+44+7557+526+550> | w. www.6point6.co.uk <http://www.6point6.co.uk/>
Sending SIGHUP instructs the running server to reload the configuration
file. Using "service" to restart would actually tell the OS to stop the
current instance of the server and then restart it.
Thomas
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
