Docs build

13 years ago · 4a184b57c8
parent d5c239404b
commit 4a184b57c8
7 changed files with 10 additions and 13 deletions
--- a/examples.html
+++ b/examples.html
@ -282,12 +282,11 @@ to poll, it looks like this:</p>
 <p>The above example says &#8220;run for 60 minutes max (60*60=3600), poll for status every 60 seconds&#8221;.
 Poll mode is smart so all jobs will be started before polling will begin on any machine.
 Be sure to use a high enough <cite>&#8211;forks</cite> value if you want to get all of your jobs started
-very quickly.</p>
+very quickly. After the time limit (in seconds) runs out (<tt class="docutils literal"><span class="pre">-B</span></tt>), the process on
+the remote nodes will be terminated.</p>
 <p>Any module other than <a class="reference internal" href="modules.html#copy"><em>copy</em></a> or <a class="reference internal" href="modules.html#template"><em>template</em></a> can be
 backgrounded.  Typically you&#8217;ll be backgrounding shell commands or
 software upgrades only.</p>
-<p>After the time limit (in seconds) runs out (<tt class="docutils literal"><span class="pre">-B</span></tt>), the process on
-the remote nodes will be killed.  Forcibly.</p>
 </div>
 </div>

--- a/index.html
+++ b/index.html
@ -183,8 +183,8 @@ much learning curve.  Ansible is dead simple and painless to extend.
 For comparison, Puppet and Chef have about 60k lines of code.
 Ansible&#8217;s core is a little over 1000 lines.</p>
 <p>Ansible isn&#8217;t just for configuration &#8211; it&#8217;s also great for Ad-Hoc
-tasks, quickly firing off commands against nodes.  See <a class="reference internal" href="examples.html"><em>Command Line Examples</em></a>.</p>
-<p>Where Ansible excels though, is expressing complex multi-node
+tasks, quickly firing off commands against nodes.  See <a class="reference internal" href="examples.html"><em>Command Line Examples</em></a>.
+Where Ansible excels though, is expressing complex multi-node
 deployment processes, executing complex sequences of commands on
 different hosts through <a class="reference internal" href="playbooks.html"><em>Playbooks</em></a>.</p>
 <p>Extending ansible does not require programming in any particular
@ -346,4 +346,4 @@ Puppet Labs, and rPath.  Reach Michael by email <a class="reference external" hr
  </div>
 </footer>
  </body>
-</html>
+</html>
--- a/man/ansible-playbook.1.html
+++ b/man/ansible-playbook.1.html
@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible-playbook</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible-playbook" lang="en"><a id="id347438"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible-playbook — run an ansible playbook</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible-playbook &lt;filename.yml&gt; … [options]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible playbooks</strong></span> are a configuration and multinode deployment system.  Ansible-playbook is the tool
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible-playbook</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible-playbook" lang="en"><a id="id571079"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible-playbook — run an ansible playbook</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible-playbook &lt;filename.yml&gt; … [options]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible playbooks</strong></span> are a configuration and multinode deployment system.  Ansible-playbook is the tool
 used to run them.   See the project home page (link below) for more information.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term">
 <span class="strong"><strong>filename.yml</strong></span>
 </span></dt><dd>
--- a/man/ansible.1.html
+++ b/man/ansible.1.html
@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible" lang="en"><a id="id487349"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible — run a command somewhere else</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible &lt;host-pattern&gt; [-f forks] [-m module_name] [-a args]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible</strong></span> is an extra-simple tool/framework/API for doing 'remote things' over
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible" lang="en"><a id="id452499"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible — run a command somewhere else</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible &lt;host-pattern&gt; [-f forks] [-m module_name] [-a args]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible</strong></span> is an extra-simple tool/framework/API for doing 'remote things' over
 SSH.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term">
 <span class="strong"><strong>host-pattern</strong></span>
 </span></dt><dd>
--- a/rst/examples.rst
+++ b/rst/examples.rst
@ -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.
  


--- a/rst/index.rst
+++ b/rst/index.rst
@ -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`.
--- a/searchindex.js
+++ b/searchindex.js