diff options
| author | prasadpatil49 <51715670+prasadpatil49@users.noreply.github.com> | 2022-11-10 13:35:02 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-10 13:35:02 +0300 |
| commit | f9451dfaf89bbab83e6ec19fc7e3954c83ec4f13 (patch) | |
| tree | 92df94b47c2425177fc932788de6caca5a7a2aeb | |
| parent | 183c34db6570472ced06e38c8be79c78150e1f4b (diff) | |
docfix for ssh_args FAQ (#79308)
| -rw-r--r-- | docs/docsite/rst/reference_appendices/faq.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docsite/rst/reference_appendices/faq.rst b/docs/docsite/rst/reference_appendices/faq.rst index 79772d963ce..cb490edd696 100644 --- a/docs/docsite/rst/reference_appendices/faq.rst +++ b/docs/docsite/rst/reference_appendices/faq.rst @@ -138,7 +138,7 @@ or globally by setting ``ssh_args`` in ``ansible.cfg``. How do I get Ansible to notice a dead target in a timely manner? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -You can add ``-o ServerAliveInterval=NumberOfSeconds`` in ``ssh_args`` from ``ansible.cfg``. Without this option, +You can add ``-o ServerAliveInterval=NumberOfSeconds`` with the ``ssh_args`` parameter in `SSH connection plugin <https://docs.ansible.com/ansible-core/devel/collections/ansible/builtin/ssh_connection.html#parameter-ssh_args>`_. Without this option, SSH and therefore Ansible will wait until the TCP connection times out. Another solution is to add ``ServerAliveInterval`` into your global SSH configuration. A good value for ``ServerAliveInterval`` is up to you to decide; keep in mind that ``ServerAliveCountMax=3`` is the SSH default so any value you set will be tripled before terminating the SSH session. |