ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-20 02:53:57 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

Docs build

Browse source
This commit is contained in:
Michael DeHaan 2012-03-11 23:20:55 -04:00
commit 4a184b57c8
7 changed files with 10 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

5
rst/examples.rst
View file

@ -128,14 +128,13 @@ Polling is built-in and looks like this::
The above example says "run for 60 minutes max (60*60=3600), poll for status every 60 seconds".
Poll mode is smart so all jobs will be started before polling will begin on any machine.
Be sure to use a high enough `--forks` value if you want to get all of your jobs started
very quickly.
very quickly. After the time limit (in seconds) runs out (``-B``), the process on
the remote nodes will be terminated.
Any module other than :ref:`copy` or :ref:`template` can be
backgrounded. Typically you'll be backgrounding shell commands or
software upgrades only.
After the time limit (in seconds) runs out (``-B``), the process on
the remote nodes will be killed. Forcibly.

1
rst/index.rst
View file

@ -26,7 +26,6 @@ Ansible's core is a little over 1000 lines.
Ansible isn't just for configuration -- it's also great for Ad-Hoc
tasks, quickly firing off commands against nodes. See :doc:`examples`.
Where Ansible excels though, is expressing complex multi-node
deployment processes, executing complex sequences of commands on
different hosts through :doc:`playbooks`.