doc: Improve debug and logging details

Explain how to enable full debug and view log output for the various
system components.

Fixes #845.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>

Author: James O. D. Hunt

README.md

@@ -94,11 +94,30 @@ $ sudo journalctl -t cc-runtime
 
 ### Enabling debug for various components
 
-The runtime, the shim (`cc-shim`), and the hypervisor all have separate debug
-options in the [configuration file](#Configuration).
+The runtime, the shim (`cc-shim`), the hypervisor and the proxy all have separate `enable_debug=` debug
+options in the [configuration file](#Configuration). Look at the comments in
+the installed configuration file for further details.
 
-The proxy (`cc-proxy`) has a command-line option to enable debug output. See
-the [proxy documentation](https://github.com/clearcontainers/proxy#debugging) for further details.
+If you wish to enable debug for all components, assuming a standard configuration file path, run:
+
+```bash
+$ sudo sed -i -e 's/^#\(enable_debug\).*=.*$/\1 = true/g' /usr/share/defaults/clear-containers/configuration.toml
+```
+
+To view shim log output:
+
+```bash
+$ sudo journalctl -t cc-shim
+```
+
+To view proxy log output:
+
+```bash
+$ sudo journalctl -t cc-proxy
+```
+
+Note that the proxy log entries also include output from `cc-agent` and the
+hypervisor (which includes the guest kernel boot-time messages).
 
 ## Limitations