From 63c3fc623c0a66c72a6d9782f31972e0fabb7202 Mon Sep 17 00:00:00 2001 From: David Wilson Date: Wed, 14 Mar 2018 19:46:54 +0545 Subject: [PATCH] docs: note the semantic difference in Mitogen vs. Ansible timeouts Related to issue #141. --- docs/ansible.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/ansible.rst b/docs/ansible.rst index b34d2b03..6de64223 100644 --- a/docs/ansible.rst +++ b/docs/ansible.rst @@ -171,6 +171,16 @@ Low Risk Behavioural Differences ----------------------- +* Mitogen treats connection timeouts for the SSH and become steps of a task + invocation separately, meaning that in some circumstances the configured + timeout may appear to be doubled. This is since Mitogen internally treats the + creation of an SSH account context separately to the creation of a sudo + account context proxied via that SSH account. + + A future revision may detect a sudo account context created immediately + following its parent SSH account, and try to emulate Ansible's existing + timeout semantics. + * Normally with Ansible, diagnostics and use of the :py:mod:`logging` package output on the target machine are discarded. With Mitogen, all of this is captured and returned to the host machine, where it can be viewed as desired