openstack
/
oslo.service
Code Issues Proposed changes

Document termination of children on SIGHUP 

Change I3e7264a1efcbf66a9afc69d8ed20f600c985c296 chenged behavior of
services when they receive SIGHUP. This needs to be documented.

Change-Id: I5a8de19ba4d7a5e2b27d88da8668f6171b7b2112
This commit is contained in:
Elena Ezhova 2015-10-14 14:08:05 +03:00
parent 5832c6fbcc
commit f566c54864
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/usage.rst
View File

@ -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.