openstack/magnum
Code Issues Proposed changes

SIGUSR1 is deprecated in Guru mediation

Browse Source 
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for
backward compatibility. SIGUSR1 will no longer be registered in
a future release, so please use SIGUSR2 to generate reports[1].

[1]http://docs.openstack.org/developer/oslo.reports/usage.html

Change-Id: I2bd1956abfe6a94dc4135ba9810eb55e0acc6e74
Closes-Bug: #1528758
This commit is contained in:
Hua Wang 2015-12-23 14:30:24 +08:00
parent aa82107e7b
commit ec1b5c1c3d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/gmr.rst
View File

@ -23,12 +23,12 @@ is called a *Guru Meditation Report* (*GMR* for short).
Generating a GMR
----------------
A *GMR* can be generated by sending the *USR1* signal to any Magnum process
A *GMR* can be generated by sending the *USR2* signal to any Magnum process
with support (see below). The *GMR* will then be outputted as standard error
for that particular process.
For example, suppose that ``magnum-api`` has process id ``8675``, and was run
with ``2>/var/log/magnum/magnum-api-err.log``. Then, ``kill -USR1 8675`` will
with ``2>/var/log/magnum/magnum-api-err.log``. Then, ``kill -USR2 8675`` will
trigger the Guru Meditation report to be printed to
``/var/log/magnum/magnum-api-err.log``.