openstack/oslo.service
Code Issues Proposed changes

Update "Signal handling" section of usage docs

Browse Source 
* Add SIGINT to the list of handled signals.
* Add a note that SIGHUP is not supported on Windows.

Change-Id: I90a1b422e00a5d2978e74f3798e17d58a58572bc
Related-Bug: #1481607
This commit is contained in:
Elena Ezhova 2015-08-13 16:06:14 +03:00
parent 5800337edd
commit 0e3c918e88
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/usage.rst
View File

@ -120,7 +120,7 @@ ProcessLauncher classes per process.
Signal handling
~~~~~~~~~~~~~~~
oslo_service.service provides handlers for such signals as SIGTERM and SIGHUP.
oslo_service.service provides handlers for such signals as SIGTERM, SIGINT and SIGHUP.
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.
@ -129,6 +129,8 @@ On receiving SIGHUP configuration files are reloaded and a service is being rese
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.
*NOTE:* SIGHUP is not supported on Windows.
Below is the example of a service with a reset method that allows reloading logging options by sending a SIGHUP.
::