cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Docfix: checking a background task

Browse source 
Minor changes to wording on how to check a background task with async_status.

Fixes #9740
This commit is contained in:
Lorin Hochstein 2014-12-08 21:52:03 -05:00
parent c725aa5e47
commit c4d5e9195b
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docsite/rst/intro_adhoc.rst
View file

@ -225,16 +225,16 @@ Ensure a service is stopped::
Time Limited Background Operations Time Limited Background Operations
`````````````````````````````````` ``````````````````````````````````
Long running operations can be backgrounded, and their status can be Long running operations can be backgrounded, and their status can be checked on
checked on later. The same job ID is given to the same task on all later. If you kick hosts and don't want to poll, it looks like this::
hosts, so you won't lose track. If you kick hosts and don't want
to poll, it looks like this::
$ ansible all -B 3600 -P 0 -a "/usr/bin/long_running_operation --do-stuff" $ ansible all -B 3600 -P 0 -a "/usr/bin/long_running_operation --do-stuff"
If you do decide you want to check on the job status later, you can:: If you do decide you want to check on the job status later, you can use the
async_status module, passing it the job id that was returned when you ran
the original job in the background::
$ ansible all -m async_status -a "jid=123456789" $ ansible web1.example.com -m async_status -a "jid=488359678239.2844"
Polling is built-in and looks like this:: Polling is built-in and looks like this::