Changeset 8368 for 2.0


Ignore:
Timestamp:
Aug 17, 2010, 7:24:15 PM (14 years ago)
Author:
richardvm
Message:

nrpe update

File:
1 edited

Legend:

Unmodified
Added
Removed

  • 2.0/nanobsd/nanobsd/files/usr/local/etc/nrpe.cfg

    r7465 r8368  
    1 #############################################################################
    2 # Sample NRPE Config File
    3 # Written by: Ethan Galstad (nagios@nagios.org)
    4 #
    5 # Last Modified: 12-30-2002
    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 
    201server_port=5666
    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=127.0.0.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 # COMMAND ARGUMENT PROCESSING
    47 # This option determines whether or not the NRPE daemon will allow clients
    48 # to specify arguments to commands that are executed.  This option only works
    49 # if the daemon was configured with the --enable-command-args configure script
    50 # option. 
    51 #
    52 # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
    53 # Read the SECURITY file for information on some of the security implications
    54 # of enabling this variable.
    55 #
    56 # Values: 0=do not allow arguments, 1=allow command arguments
    57 
    58 dont_blame_nrpe=1
    59 
    60 
    61 # NRPE USER
    62 # This determines the effective user that the NRPE daemon should run as. 
    63 # You can either supply a username or a UID.
    64 #
    65 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
    66 
     2allowed_hosts=172.16.4.46
    673nrpe_user=nagios
    68 
    69 
    70 
    71 # NRPE GROUP
    72 # This determines the effective group that the NRPE daemon should run as. 
    73 # You can either supply a group name or a GID.
    74 #
    75 # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
    76 
    774nrpe_group=nagios
    78 
    79 
    80 
    81 # DEBUGGING OPTION
    82 # This option determines whether or not debugging messages are logged to the
    83 # syslog facility.
    84 # Values: 0=debugging off, 1=debugging on
    85 
    86 debug=0
    87 
    88 
    89 
    90 # COMMAND TIMEOUT
    91 # This specifies the maximum number of seconds that the NRPE daemon will
    92 # allow plugins to finish executing before killing them off.
    93 
    945command_timeout=60
    95 
    96 
    97 
    98 # COMMAND DEFINITIONS
    99 # Command definitions that this daemon will run.  Definitions
    100 # are in the following format:
    101 #
    102 # command[<command_name>]=<command_line>
    103 #
    104 # When the daemon receives a request to return the results of <command_name>
    105 # it will execute the command specified by the <command_line> argument.
    106 #
    107 # Unlike Nagios, the command line cannot contain macros - it must be
    108 # typed exactly as it should be executed.
    109 #
    110 # Note: Any plugins that are used in the command lines must reside
    111 # on the machine that this daemon is running on!  The examples below
    112 # assume that you have plugins installed in a /usr/local/nagios/libexec
    113 # directory.  Also note that you will have to modify the definitions below
    114 # to match the argument format the plugins expect.  Remember, these are
    115 # examples only!
    1166
    1177command[check_users]=/usr/local/libexec/nagios/check_users -w 5 -c 10
    1188command[check_load]=/usr/local/libexec/nagios/check_load -w 15,10,5 -c 30,25,20
    119 command[check_disk1]=/usr/local/libexec/nagios/check_disk -w 20 -c 10 -p /dev/hda1
    120 command[check_disk2]=/usr/local/libexec/nagios/check_disk -w 20 -c 10 -p /dev/hdb1
    121 command[check_zombie_procs]=/usr/local/libexec/nagios/check_procs -w 5 -c 10 -s Z
    122 command[check_total_procs]=/usr/local/libexec/nagios/check_procs -w 150 -c 200
     9command[check_disk1]=/usr/local/libexec/nagios/check_disk -w 20% -c 10% -p /
     10command[check_disk2]=/usr/local/libexec/nagios/check_disk -w 20% -c 10% -p /var
     11command[check_procs]=/usr/local/libexec/nagios/check_procs -w 55 -c 70
     12
Note: See TracChangeset for help on using the changeset viewer.