From ec1b5c1c3d30bd8d5c48c4bb5c364d96fd96ee0f Mon Sep 17 00:00:00 2001 From: Hua Wang Date: Wed, 23 Dec 2015 14:30:24 +0800 Subject: [PATCH] SIGUSR1 is deprecated in Guru mediation 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 --- doc/source/gmr.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/gmr.rst b/doc/source/gmr.rst index 577b77f0f2..74fd485f9d 100644 --- a/doc/source/gmr.rst +++ b/doc/source/gmr.rst @@ -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``.