From c4d5e9195ba7e33f81383cea8daf4f904fc577a2 Mon Sep 17 00:00:00 2001 From: Lorin Hochstein Date: Mon, 8 Dec 2014 21:52:03 -0500 Subject: [PATCH] Docfix: checking a background task Minor changes to wording on how to check a background task with async_status. Fixes #9740 --- docsite/rst/intro_adhoc.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docsite/rst/intro_adhoc.rst b/docsite/rst/intro_adhoc.rst index 770c2bd5be6..2978343abe0 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::