From f566c54864e16c811c5510f210e6070a92eab8ba Mon Sep 17 00:00:00 2001 From: Elena Ezhova Date: Wed, 14 Oct 2015 14:08:05 +0300 Subject: [PATCH] Document termination of children on SIGHUP Change I3e7264a1efcbf66a9afc69d8ed20f600c985c296 chenged behavior of services when they receive SIGHUP. This needs to be documented. Change-Id: I5a8de19ba4d7a5e2b27d88da8668f6171b7b2112 --- doc/source/usage.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/usage.rst b/doc/source/usage.rst index 02f4e5a1..153fc638 100644 --- a/doc/source/usage.rst +++ b/doc/source/usage.rst @@ -128,9 +128,9 @@ oslo_service.service provides handlers for such signals as SIGTERM, SIGINT and S SIGTERM is used for graceful termination of services. This can allow a server to wait for all clients to close connections while rejecting new incoming requests. To force instantaneous termination SIGINT signal must be sent. -On receiving SIGHUP configuration files are reloaded and a service is being reset and started again.Thus, SIGHUP -can be used for changing config options on the go. To achieve this each service should implement a *reset* method -which actually enforces changes to config options values. +On receiving SIGHUP configuration files are reloaded and a service is being reset and started again. Then all child +workers are gracefully stopped using SIGTERM and workers with new configuration are spawned. Thus, SIGHUP can be used +for changing config options on the go. *NOTE:* SIGHUP is not supported on Windows.