summaryrefslogtreecommitdiff
path: root/docsite
diff options
context:
space:
mode:
authorToshio Kuratomi <a.badger@gmail.com>2014-12-09 09:23:43 -0800
committerToshio Kuratomi <a.badger@gmail.com>2014-12-09 09:23:43 -0800
commit5a9e4408df1f8b3b83a774b1177927a69dbca30e (patch)
tree8ba7be30fa673a5afb608ab12a72f1dbb21a5407 /docsite
parentc16b83af14b13e84887169ef6470cfb1d3d589c4 (diff)
parentc4d5e9195ba7e33f81383cea8daf4f904fc577a2 (diff)
downloadansible-5a9e4408df1f8b3b83a774b1177927a69dbca30e.tar.gz
Merge pull request #9751 from lorin/doc-async
Docfix: checking a background task
Diffstat (limited to 'docsite')
-rw-r--r--docsite/rst/intro_adhoc.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docsite/rst/intro_adhoc.rst b/docsite/rst/intro_adhoc.rst
index 770c2bd5be..2978343abe 100644
--- a/docsite/rst/intro_adhoc.rst
+++ b/docsite/rst/intro_adhoc.rst
@@ -225,16 +225,16 @@ Ensure a service is stopped::
Time Limited Background Operations
``````````````````````````````````
-Long running operations can be backgrounded, and their status can be
-checked on later. The same job ID is given to the same task on all
-hosts, so you won't lose track. If you kick hosts and don't want
-to poll, it looks like this::
+Long running operations can be backgrounded, and their status can be checked on
+later. 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"
-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::