From 8840da4a211e59c50d9bfc3ffd993544a221bd2c Mon Sep 17 00:00:00 2001 From: basilfx Date: Thu, 18 Sep 2014 02:10:48 -0700 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 32e7010..40a4c36 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -4,7 +4,7 @@ This page presents some guides to help fix common problems. If your problem is n Headphones does not turn on verbose logging (also known as debug information) for efficiency reasons. While this information is extremely useful in solving problems, it is the first thing that you should enable in case of problems. There are two ways of toggling verbose mode. * Modify the command line arguments to include the `--verbose` (or `-v`) option. Do note that the `--verbose` option may conflicts with `--quiet` (web log only) and `--daemon` (no terminal output), but it will always print to the web log. -* Toggle verbose mode via `http://ip:port/toggleVerbose`. You should see in the web log if verbose is turned on or off. This option is not permanent, and will be restored on the next start. With this option, you cannot log startup errors, since Headphones should be started to toggle this. +* Toggle verbose mode via `http://ip:port/toggleVerbose`. You should see in the web log if verbose is turned on or off. This option is **not permanent**, and will be restored on the next start. With this option, you cannot log startup errors, since Headphones should be started to toggle this. The second option will be the easiest option in most cases, especially for Synology users.