From 537a263261ceb6ef0dae9df8fa5b93533b244b67 Mon Sep 17 00:00:00 2001 From: David Wilson Date: Thu, 8 Mar 2018 17:27:41 +0545 Subject: [PATCH] docs: So many typos --- docs/ansible.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/ansible.rst b/docs/ansible.rst index 6afd21e0..e0001324 100644 --- a/docs/ansible.rst +++ b/docs/ansible.rst @@ -234,16 +234,17 @@ Debugging Mitogen's logs are integrated into Ansible's display framework. Basic high level debug logs are produced with ``-vvv``, with logging of all IO activity on -the controller machine with ``-vvvv``. +the controller machine when ``-vvvv`` or higher is specified. -It is not possible to receive IO activity logs from children spawned on remote -machines, as the processs of receiving those woulds would in turn generate more -logs To receive a complete trace of every process, file-based logging is -required, which can be enabled by setting ``MITOGEN_ROUTER_DEBUG=1`` in your -environment. +Although any use of standard IO and the logging package on remote machines is +forwarded to the controller machine, it is not possible to receive logs of all +IO activity, as the processs of receiving those logs would would in turn +generate more IO activity. To receive a complete trace of every process on +every machine, file-based logging is required. File-based logging can be +enabled by setting ``MITOGEN_ROUTER_DEBUG=1`` in your environment. When file-based logging is enabled, one file per context will be created on the -target machines, as ``/tmp/mitogen..log``. +local machine and every target machine, as ``/tmp/mitogen..log``. Implementation Notes