fixed permissions on command.cfg file
This commit is contained in:
@@ -83,11 +83,10 @@ There are currently no mandatory parameters, i.e. the module will function right
|
||||
|
||||
### Optional Parameters
|
||||
|
||||
* `$ne_manage_cmds` : Whether to manage check command definitions dynamically through a define, i.e. from other Puppet modules or profiles. Defaults to `true`.
|
||||
* `$ne_incl_fw` : Whether to manage relevant firewall rules through this modules. Defaults to `true`.
|
||||
* `$ne_include_selinux` : Whether to manage selinux exception rules. Defaults to `true`.
|
||||
* `$ne_enable_ssl` : Whether to allow SSL settings. See [known problems](#konwn-problems) for more details.
|
||||
|
||||
* `$ne_manage_cmds` : Whether to manage check command definitions dynamically through a define, i.e. from other Puppet modules or profiles. Defaults to `true`.
|
||||
* `$ne_incl_fw` : Whether to manage relevant firewall rules through this modules. Defaults to `true`.
|
||||
* `$ne_include_selinux` : Whether to manage selinux exception rules. Defaults to `true`.
|
||||
* `$ne_enable_ssl` : Whether to allow SSL settings. See [known problems](#konwn-problems) for more details.
|
||||
|
||||
### Managing Check Commands
|
||||
In order to connect a Nagios monitoring server to clients through NRPE, you 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.
|
||||
|
||||
Reference in New Issue
Block a user