recommit for updates in build 43
This commit is contained in:
@@ -218,7 +218,29 @@ rules. Defaults to <code>true</code>.</p>
|
||||
<h3 id="label-Managing+Check+Commands">Managing Check Commands</h3>
|
||||
|
||||
<p>In order to connect a Nagios monitoring server to clients through NRPE, you
|
||||
must define commands and the desired argument strings on the clients.</p>
|
||||
must define commands and the desired argument strings on the clients. The
|
||||
default NRPE installation comes with a few examples of such commands, which
|
||||
are also included in this module. However, every environment is very
|
||||
different in their requirements and Nagios via Puppet is all about the
|
||||
ability to dynamicically set command arguments based on default variables /
|
||||
overrides. For that reason no hard-coded commands are included, but instead
|
||||
all commands are set via argument strings, where possible.</p>
|
||||
|
||||
<p>Defining commands is as simple as
|
||||
that:
|
||||
<code>
|
||||
`cd_nrpe::commands::definitions` {
|
||||
'check_users':
|
||||
`ne_check_cmd` =>
|
||||
'check_users',
|
||||
`ne_cmd_argstring` => '-w $ARG1$ -c
|
||||
$ARG2$',
|
||||
}
|
||||
</code>
|
||||
It is very recommendable to define such
|
||||
commands within Puppet modules controlling services, so any node running
|
||||
the particular service will automatically get the required check commands
|
||||
defined as well.</p>
|
||||
|
||||
<h3 id="label-SELINUX">SELINUX</h3>
|
||||
|
||||
@@ -280,7 +302,7 @@ environments.</p>
|
||||
</div></div>
|
||||
|
||||
<div id="footer">
|
||||
Generated on Sun Jul 30 13:50:44 2017 by
|
||||
Generated on Sun Jul 30 14:07:45 2017 by
|
||||
<a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
|
||||
0.9.9 (ruby-2.0.0).
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user