From 716bbf2ebe67a63ff5c48cc812489bbcbdd3a894 Mon Sep 17 00:00:00 2001
From: 12ww1160 <12ww1160@confdroid.com>
Date: Wed, 11 Mar 2026 16:58:52 +0100
Subject: [PATCH] change requirement

---
 README.md                              | 5 +++++
 manifests/commands/definition_rules.pp | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 459ea13..5c7bff0 100644
--- a/README.md
+++ b/README.md
@@ -86,11 +86,16 @@ Defining commands is as simple as that:
 
 ```ruby
 confdroid_nrpe::commands::definitions { 'check_users':
+      ne_check_name     => 'check_users',
       ne_check_cmd      =>  'check_users',
       ne_cmd_argstring  =>  '-w $ARG1$ -c $ARG2$',
     }
 ```
 
+>Q: `ne_check_name` is the same as `ne_check_cmd`, why is that?
+A: Sometimes the name of the check is different, like this:
+`command[check_fail2ban]=/usr/lib/nagios/plugins/check_procs -c 1:1 -a fail2ban-server`
+
 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
diff --git a/manifests/commands/definition_rules.pp b/manifests/commands/definition_rules.pp
index 7edc258..826eaad 100644
--- a/manifests/commands/definition_rules.pp
+++ b/manifests/commands/definition_rules.pp
@@ -46,7 +46,7 @@ class confdroid_nrpe::commands::definition_rules (
       ne_cmd_argstring => '-w $ARG1$ -c $ARG2$',
       ne_cmd_comment   => 'check the amount of user logged in locally',
     }
-  
+
     confdroid_nrpe::commands::definitions { 'check_load':
       ne_check_name    => 'check_load',
       ne_check_cmd     => 'check_load',