docs: Explain -v/-vv/-vvv differences

This commit is contained in:
Stein Magnus Jodal 2014-01-12 01:44:34 +01:00
parent c7240141c2
commit 94c904815d

View File

@ -25,8 +25,8 @@ mailing list or when reporting an issue, somewhat longer text dumps are
accepted, but large logs should still be shared through a pastebin.
Effective configuration
=======================
Show effective configuration
============================
The command ``mopidy config`` will print your full effective
configuration the way Mopidy sees it after all defaults and all config files
@ -35,8 +35,8 @@ passwords are masked out, so the output of the command should be safe to share
with others for debugging.
Installed dependencies
======================
Show installed dependencies
===========================
The command ``mopidy deps`` will list the paths to and versions of
any dependency Mopidy or the extensions might need to work. This is very useful
@ -48,11 +48,16 @@ your system.
Debug logging
=============
If you run :option:`mopidy -v`, Mopidy will output debug log to stdout. If you
run :option:`mopidy --save-debug-log`, it will save the debug log to the file
``mopidy.log`` in the directory you ran the command from.
If you run :option:`mopidy -v` or ``mopidy -vv`` or ``mopidy -vvv`` Mopidy will
print more and more debug log to stdout. All three options will give you debug
level output from Mopidy and extensions, while ``-vv`` and ``-vvv`` will give
you more log output from their dependencies as well.
If you want to turn on more or less logging for some component, see the
If you run :option:`mopidy --save-debug-log`, it will save the log equivalent
with ``-vvv`` to the file ``mopidy.log`` in the directory you ran the command
from.
If you want to reduce the logging for some component, see the
docs for the :confval:`loglevels/*` config section.