confdroid/confdroid_nrpe
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

TODO-0001 - markdown lint

Browse Source
This commit is contained in:
Arne Teuke
2021-09-13 15:38:55 +02:00
parent ba1890120c
commit 117c0fef23
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -76,14 +76,15 @@ In order to connect a Nagios monitoring server to clients through NRPE, you must
The commands are created within /etc/nrpe.d/command.cfg , every set of instructions creates a new line. The commands are created within /etc/nrpe.d/command.cfg , every set of instructions creates a new line.
Defining commands is as simple as that: Defining commands is as simple as that:
```
```ruby
cd_nrpe::commands::definitions { 'check_users': cd_nrpe::commands::definitions { 'check_users':
ne_check_cmd => 'check_users', ne_check_cmd => 'check_users',
ne_cmd_argstring => '-w $ARG1$ -c $ARG2$', ne_cmd_argstring => '-w $ARG1$ -c $ARG2$',
} }
``` ```
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.
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.
## SELINUX ## SELINUX