andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: Recommend pkill instead of ps+kill

Browse Source
This commit is contained in:
Stein Magnus Jodal 2013-03-24 01:05:53 +01:00
parent f843b32e88
commit c1c5fff01f
1 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/development.rst
View File

@ -308,21 +308,10 @@ sometimes be a potential for deadlocks. In an effort to make these slightly
simpler to debug Mopidy registers a ``SIGUSR1`` signal handler which logs the
traceback of all alive threads.
To trigger the signal handler, you need the process ID (PID) of Mopidy. This
can for example be found by running ``ps``::
To trigger the signal handler, you can use the ``pkill`` command to
send the ``SIGUSR1`` signal to any Mopidy processes::
$ ps aux | grep mopidy
jodal 4313 2.0 1.7 2573592 69804 pts/14 Sl+ 00:15 0:02 python
mopidy
jodal 4700 0.0 0.0 9392 924 pts/10 S+ 00:17 0:00 grep
mopidy
$
In this example, Mopidy's PID is 4313. You can then use the ``kill`` command to
send the ``SIGUSR1`` signal to the Mopidy proces::
$ kill -SIGUSR1 4313
$
pkill -SIGUSR1 mopidy
If you check the log, you should now find one log record with a full traceback
for each of the currently alive threads in Mopidy.