« back to all changes in this revision
Viewing changes to nrpe.cfg.in
- browse files at revision 1
- compare with another revision
- download diff
- download tarball
- view history from revision 1
- Committer: Bazaar Package Importer
- Author(s): Jason Thomas
- Date: 2004-05-15 12:02:35 UTC
- Revision ID: james.westby@ubuntu.com-20040515120235-52bbrpj39ss7wlvu
Tags: upstream-2.0
Import upstream version 2.0
- files added:
- common
- contrib
- src
added
removed
nrpe.cfg.in
1
#############################################################################
2
# Sample NRPE Config File
3
# Written by: Ethan Galstad (nagios@nagios.org)
4
#
5
# Last Modified: 03-05-2003
6
#
7
# NOTES:
8
# This is a sample configuration file for the NRPE daemon. It needs to be
9
# located on the remote host that is running the NRPE daemon, not the host
10
# from which the check_nrpe client is being executed.
11
#############################################################################
12
13
14
15
# PORT NUMBER
16
# Port number we should wait for connections on.
17
# NOTE: This must be a non-priviledged port (i.e. > 1024).
18
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
19
20
server_port=@nrpe_port@
21
22
23
24
# SERVER ADDRESS
25
# Address that nrpe should bind to in case there are more than one interface
26
# and you do not want nrpe to bind on all interfaces.
27
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
28
29
#server_address=192.168.1.1
30
31
32
33
# ALLOWED HOST ADDRESSES
34
# This is a comma-delimited list of IP address of hosts that are allowed
35
# to talk to the NRPE daemon.
36
#
37
# NOTE: The daemon only does rudimentary checking of the client's IP
38
# address. I would highly recommend adding entries in your
39
# /etc/hosts.allow file to allow only the specified host to connect
40
# to the port you are running this daemon on.
41
#
42
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
43
44
allowed_hosts=127.0.0.1
45
46
47
48
# NRPE USER
49
# This determines the effective user that the NRPE daemon should run as.
50
# You can either supply a username or a UID.
51
#
52
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
53
54
nrpe_user=@nrpe_user@
55
56
57
58
# NRPE GROUP
59
# This determines the effective group that the NRPE daemon should run as.
60
# You can either supply a group name or a GID.
61
#
62
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
63
64
nrpe_group=@nrpe_grp@
65
66
67
68
# COMMAND ARGUMENT PROCESSING
69
# This option determines whether or not the NRPE daemon will allow clients
70
# to specify arguments to commands that are executed. This option only works
71
# if the daemon was configured with the --enable-command-args configure script
72
# option.
73
#
74
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
75
# Read the SECURITY file for information on some of the security implications
76
# of enabling this variable.
77
#
78
# Values: 0=do not allow arguments, 1=allow command arguments
79
80
dont_blame_nrpe=0
81
82
83
84
# DEBUGGING OPTION
85
# This option determines whether or not debugging messages are logged to the
86
# syslog facility.
87
# Values: 0=debugging off, 1=debugging on
88
89
debug=0
90
91
92
93
# COMMAND TIMEOUT
94
# This specifies the maximum number of seconds that the NRPE daemon will
95
# allow plugins to finish executing before killing them off.
96
97
command_timeout=60
98
99
100
101
# INCLUDE CONFIG FILE
102
# This directive allows you to include definitions from an external config file.
103
104
#include=<somefile.cfg>
105
106
107
108
# INCLUDE CONFIG DIRECTORY
109
# This directive allows you to include definitions from config files (with a
110
# .cfg extension) in one or more directories (with recursion).
111
112
#include_dir=<somedirectory>
113
#include_dir=<someotherdirectory>
114
115
116
117
# COMMAND DEFINITIONS
118
# Command definitions that this daemon will run. Definitions
119
# are in the following format:
120
#
121
# command[<command_name>]=<command_line>
122
#
123
# When the daemon receives a request to return the results of <command_name>
124
# it will execute the command specified by the <command_line> argument.
125
#
126
# Unlike Nagios, the command line cannot contain macros - it must be
127
# typed exactly as it should be executed.
128
#
129
# Note: Any plugins that are used in the command lines must reside
130
# on the machine that this daemon is running on! The examples below
131
# assume that you have plugins installed in a /usr/local/nagios/libexec
132
# directory. Also note that you will have to modify the definitions below
133
# to match the argument format the plugins expect. Remember, these are
134
# examples only!
135
136
# The following examples use hardcoded command arguments...
137
138
command[check_users]=@libexecdir@/check_users -w 5 -c 10
139
command[check_load]=@libexecdir@/check_load -w 15,10,5 -c 30,25,20
140
command[check_disk1]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hda1
141
command[check_disk2]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hdb1
142
command[check_zombie_procs]=@libexecdir@/check_procs -w 5 -c 10 -s Z
143
command[check_total_procs]=@libexecdir@/check_procs -w 150 -c 200
144
145
# The following examples allow user-supplied arguments and can
146
# only be used if the NRPE daemon was compiled with support for
147
# command arguments *AND* the dont_blame_nrpe directive in this
148
# config file is set to '1'...
149
150
#command[check_users]=@libexecdir@/check_users -w $ARG1$ -c $ARG2$
151
#command[check_load]=@libexecdir@/check_load -w $ARG1$ -c $ARG2$
152
#command[check_disk]=@libexecdir@/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
153
#command[check_procs]=@libexecdir@/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
Loggerhead is a web-based interface for Breezy
Version: 2.0.1