Commit 537a2632 authored by David Wilson's avatar David Wilson

docs: So many typos

parent 6bd4c5ea
...@@ -234,16 +234,17 @@ Debugging ...@@ -234,16 +234,17 @@ Debugging
Mitogen's logs are integrated into Ansible's display framework. Basic high 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 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 Although any use of standard IO and the logging package on remote machines is
machines, as the processs of receiving those woulds would in turn generate more forwarded to the controller machine, it is not possible to receive logs of all
logs To receive a complete trace of every process, file-based logging is IO activity, as the processs of receiving those logs would would in turn
required, which can be enabled by setting ``MITOGEN_ROUTER_DEBUG=1`` in your generate more IO activity. To receive a complete trace of every process on
environment. 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 When file-based logging is enabled, one file per context will be created on the
target machines, as ``/tmp/mitogen.<pid>.log``. local machine and every target machine, as ``/tmp/mitogen.<pid>.log``.
Implementation Notes Implementation Notes
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment