Recommit for updates in build 36

doc/file.README.html

@@ -175,11 +175,16 @@
 <p>Defining commands is as simple as that:</p>
 
 <pre class="code ruby"><code class="ruby">confdroid_nrpe::commands::definitions { &#39;check_users&#39;:
+      ne_check_name     =&gt; &#39;check_users&#39;,
       ne_check_cmd      =&gt;  &#39;check_users&#39;,
       ne_cmd_argstring  =&gt;  &#39;-w $ARG1$ -c $ARG2$&#39;,
     }
 </code></pre>
 
+<blockquote>
+<p>Q: <code>ne_check_name</code> is the same as <code>ne_check_cmd</code>, why is that? A: Sometimes the name of the check is different, like this: <code>command[check_fail2ban]=/usr/lib/nagios/plugins/check_procs -c 1:1 -a fail2ban-server</code></p>
+</blockquote>
+
 <p>It is very recommendable to define such commands directly within Puppet modules or profiles, so any node running the particular service controlled by the module will automatically get the required check commands defined as well, while nodes not running the service also do not contain the command check. The same then is true for Nagios checks, so you would have both the NRPE command definition and the Nagios check contained in Puppet modules or profiles to have it in one location.</p>
 
 <h2 id="label-SELINUX">SELINUX</h2>

doc/index.html

@@ -175,11 +175,16 @@
 <p>Defining commands is as simple as that:</p>
 
 <pre class="code ruby"><code class="ruby">confdroid_nrpe::commands::definitions { &#39;check_users&#39;:
+      ne_check_name     =&gt; &#39;check_users&#39;,
       ne_check_cmd      =&gt;  &#39;check_users&#39;,
       ne_cmd_argstring  =&gt;  &#39;-w $ARG1$ -c $ARG2$&#39;,
     }
 </code></pre>
 
+<blockquote>
+<p>Q: <code>ne_check_name</code> is the same as <code>ne_check_cmd</code>, why is that? A: Sometimes the name of the check is different, like this: <code>command[check_fail2ban]=/usr/lib/nagios/plugins/check_procs -c 1:1 -a fail2ban-server</code></p>
+</blockquote>
+
 <p>It is very recommendable to define such commands directly within Puppet modules or profiles, so any node running the particular service controlled by the module will automatically get the required check commands defined as well, while nodes not running the service also do not contain the command check. The same then is true for Nagios checks, so you would have both the NRPE command definition and the Nagios check contained in Puppet modules or profiles to have it in one location.</p>
 
 <h2 id="label-SELINUX">SELINUX</h2>

doc/puppet_classes/confdroid_nrpe_3A_3Acommands_3A_3Adefinition_rules.html

@@ -176,7 +176,12 @@
 72
 73
 74
-75</pre>
+75
+76
+77
+78
+79
+80</pre>
       </td>
       <td>
         <pre class="code"><span class="info file"># File 'manifests/commands/definition_rules.pp', line 12</span>
@@ -213,27 +218,32 @@ class confdroid_nrpe::commands::definition_rules (
     # basic example rules
 
     confdroid_nrpe::commands::definitions { &#39;check_users&#39;:
+      ne_check_name    =&gt; &#39;check_users&#39;,
       ne_check_cmd     =&gt; &#39;check_users&#39;,
       ne_cmd_argstring =&gt; &#39;-w $ARG1$ -c $ARG2$&#39;,
       ne_cmd_comment   =&gt; &#39;check the amount of user logged in locally&#39;,
     }
 
     confdroid_nrpe::commands::definitions { &#39;check_load&#39;:
+      ne_check_name    =&gt; &#39;check_load&#39;,
       ne_check_cmd     =&gt; &#39;check_load&#39;,
       ne_cmd_argstring =&gt; &#39;-w $ARG1$ -c $ARG2$&#39;,
     }
 
     confdroid_nrpe::commands::definitions { &#39;check_disk&#39;:
+      ne_check_name    =&gt; &#39;check_disk&#39;,
       ne_check_cmd     =&gt; &#39;check_disk&#39;,
       ne_cmd_argstring =&gt; &#39;-w $ARG1$ -c $ARG2$ -p $ARG3$&#39;,
     }
 
     confdroid_nrpe::commands::definitions { &#39;check_procs&#39;:
+      ne_check_name    =&gt; &#39;check_procs&#39;,
       ne_check_cmd     =&gt; &#39;check_procs&#39;,
       ne_cmd_argstring =&gt; &#39;-w $ARG1$ -c $ARG2$ -s $ARG3$&#39;,
     }
 
     confdroid_nrpe::commands::definitions { &#39;check_swap&#39;:
+      ne_check_name    =&gt; &#39;check_swap&#39;,
       ne_check_cmd     =&gt; &#39;check_swap&#39;,
       ne_cmd_argstring =&gt; &#39;-w $ARG1$ -c $ARG2$&#39;,
     }