2 ## THIS FILE IS UNDER PUPPET CONTROL. DON'T EDIT IT HERE.
3 ## USE: git clone git+ssh://$USER@puppet.debian.org/srv/puppet.debian.org/git/dsa-puppet.git
5 #############################################################################
6 # Sample NRPE Config File
7 # Written by: Ethan Galstad (nagios@nagios.org)
9 # Last Modified: 11-23-2007
12 # This is a sample configuration file for the NRPE daemon. It needs to be
13 # located on the remote host that is running the NRPE daemon, not the host
14 # from which the check_nrpe client is being executed.
15 #############################################################################
19 # The syslog facility that should be used for logging purposes.
26 # The name of the file in which the NRPE daemon should write it's process ID
27 # number. The file is only written if the NRPE daemon is started by the root
28 # user and is running in standalone mode.
30 pid_file=/var/run/nrpe.pid
35 # Port number we should wait for connections on.
36 # NOTE: This must be a non-priviledged port (i.e. > 1024).
37 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
44 # Address that nrpe should bind to in case there are more than one interface
45 # and you do not want nrpe to bind on all interfaces.
46 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
48 #server_address=127.0.0.1
53 # This determines the effective user that the NRPE daemon should run as.
54 # You can either supply a username or a UID.
56 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
63 # This determines the effective group that the NRPE daemon should run as.
64 # You can either supply a group name or a GID.
66 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
72 # ALLOWED HOST ADDRESSES
73 # This is an optional comma-delimited list of IP address or hostnames
74 # that are allowed to talk to the NRPE daemon.
76 # Note: The daemon only does rudimentary checking of the client's IP
77 # address. I would highly recommend adding entries in your /etc/hosts.allow
78 # file to allow only the specified host to connect to the port
79 # you are running this daemon on.
81 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
83 allowed_hosts=127.0.0.1
87 # COMMAND ARGUMENT PROCESSING
88 # This option determines whether or not the NRPE daemon will allow clients
89 # to specify arguments to commands that are executed. This option only works
90 # if the daemon was configured with the --enable-command-args configure script
93 # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
94 # Read the SECURITY file for information on some of the security implications
95 # of enabling this variable.
97 # Values: 0=do not allow arguments, 1=allow command arguments
104 # This option allows you to prefix all commands with a user-defined string.
105 # A space is automatically added between the specified prefix string and the
106 # command line from the command definition.
108 # *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
110 # Execute restricted commmands using sudo. For this to work, you need to add
111 # the nagios user to your /etc/sudoers. An example entry for alllowing
112 # execution of the plugins from might be:
114 # nagios ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
116 # This lets the nagios user run all commands in that directory (and only them)
117 # without asking for a password. If you do this, make sure you don't give
118 # random users write access to that directory or its contents!
120 # command_prefix=/usr/bin/sudo
125 # This option determines whether or not debugging messages are logged to the
127 # Values: 0=debugging off, 1=debugging on
134 # This specifies the maximum number of seconds that the NRPE daemon will
135 # allow plugins to finish executing before killing them off.
142 # This specifies the maximum number of seconds that the NRPE daemon will
143 # wait for a connection to be established before exiting. This is sometimes
144 # seen where a network problem stops the SSL being established even though
145 # all network sessions are connected. This causes the nrpe daemons to
146 # accumulate, eating system resources. Do not set this too low.
148 connection_timeout=300
152 # WEEK RANDOM SEED OPTION
153 # This directive allows you to use SSL even if your system does not have
154 # a /dev/random or /dev/urandom (on purpose or because the necessary patches
155 # were not applied). The random number generator will be seeded from a file
156 # which is either a file pointed to by the environment valiable $RANDFILE
157 # or $HOME/.rnd. If neither exists, the pseudo random number generator will
158 # be initialized and a warning will be issued.
159 # Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness
161 #allow_weak_random_seed=1
165 # INCLUDE CONFIG FILE
166 # This directive allows you to include definitions from an external config file.
168 #include=<somefile.cfg>
172 # INCLUDE CONFIG DIRECTORY
173 # This directive allows you to include definitions from config files (with a
174 # .cfg extension) in one or more directories (with recursion).
176 #include_dir=<somedirectory>
177 #include_dir=<someotherdirectory>
181 # COMMAND DEFINITIONS
182 # Command definitions that this daemon will run. Definitions
183 # are in the following format:
185 # command[<command_name>]=<command_line>
187 # When the daemon receives a request to return the results of <command_name>
188 # it will execute the command specified by the <command_line> argument.
190 # Unlike Nagios, the command line cannot contain macros - it must be
191 # typed exactly as it should be executed.
193 # Note: Any plugins that are used in the command lines must reside
194 # on the machine that this daemon is running on! The examples below
195 # assume that you have plugins installed in a /usr/local/nagios/libexec
196 # directory. Also note that you will have to modify the definitions below
197 # to match the argument format the plugins expect. Remember, these are
201 # The following examples use hardcoded command arguments...
203 command[check_users]=/usr/lib/nagios/plugins/check_users -w 5 -c 10
204 command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
205 command[check_hda1]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /dev/hda1
206 command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c 10 -s Z
207 command[check_total_procs]=/usr/lib/nagios/plugins/check_procs -w 150 -c 200
210 # The following examples allow user-supplied arguments and can
211 # only be used if the NRPE daemon was compiled with support for
212 # command arguments *AND* the dont_blame_nrpe directive in this
213 # config file is set to '1'. This poses a potential security risk, so
214 # make sure you read the SECURITY file before doing this.
216 #command[check_users]=/usr/lib/nagios/plugins/check_users -w $ARG1$ -c $ARG2$
217 #command[check_load]=/usr/lib/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
218 #command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
219 #command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
222 # local configuration:
223 # if you'd prefer, you can instead place directives here
224 include=/etc/nagios/nrpe_local.cfg
227 # you can place your config snipplets into nrpe.d/
228 include_dir=/etc/nagios/nrpe.d/