nrpe.cfg.in 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206
  1. #############################################################################
  2. # Sample NRPE Config File
  3. # Written by: Ethan Galstad (nagios@nagios.org)
  4. #
  5. # Last Modified: 12-11-2006
  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. # PID FILE
  13. # The name of the file in which the NRPE daemon should write it's process ID
  14. # number. The file is only written if the NRPE daemon is started by the root
  15. # user and is running in standalone mode.
  16. pid_file=/var/run/nrpe.pid
  17. # PORT NUMBER
  18. # Port number we should wait for connections on.
  19. # NOTE: This must be a non-priviledged port (i.e. > 1024).
  20. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  21. server_port=@nrpe_port@
  22. # SERVER ADDRESS
  23. # Address that nrpe should bind to in case there are more than one interface
  24. # and you do not want nrpe to bind on all interfaces.
  25. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  26. #server_address=192.168.1.1
  27. # NRPE USER
  28. # This determines the effective user that the NRPE daemon should run as.
  29. # You can either supply a username or a UID.
  30. #
  31. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  32. nrpe_user=@nrpe_user@
  33. # NRPE GROUP
  34. # This determines the effective group that the NRPE daemon should run as.
  35. # You can either supply a group name or a GID.
  36. #
  37. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  38. nrpe_group=@nrpe_grp@
  39. # ALLOWED HOST ADDRESSES
  40. # This is an optional comma-delimited list of IP address or hostnames
  41. # that are allowed to talk to the NRPE daemon.
  42. #
  43. # Note: The daemon only does rudimentary checking of the client's IP
  44. # address. I would highly recommend adding entries in your /etc/hosts.allow
  45. # file to allow only the specified host to connect to the port
  46. # you are running this daemon on.
  47. #
  48. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  49. #allowed_hosts=127.0.0.1,192.168.0.2
  50. # COMMAND ARGUMENT PROCESSING
  51. # This option determines whether or not the NRPE daemon will allow clients
  52. # to specify arguments to commands that are executed. This option only works
  53. # if the daemon was configured with the --enable-command-args configure script
  54. # option.
  55. #
  56. # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
  57. # Read the SECURITY file for information on some of the security implications
  58. # of enabling this variable.
  59. #
  60. # Values: 0=do not allow arguments, 1=allow command arguments
  61. dont_blame_nrpe=0
  62. # COMMAND PREFIX
  63. # This option allows you to prefix all commands with a user-defined string.
  64. # A space is automatically added between the specified prefix string and the
  65. # command line from the command definition.
  66. #
  67. # *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
  68. # Usage scenario:
  69. # Execute restricted commmands using sudo. For this to work, you need to add
  70. # the nagios user to your /etc/sudoers. An example entry for alllowing
  71. # execution of the plugins from might be:
  72. #
  73. # nagios ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
  74. #
  75. # This lets the nagios user run all commands in that directory (and only them)
  76. # without asking for a password. If you do this, make sure you don't give
  77. # random users write access to that directory or its contents!
  78. # command_prefix=/usr/bin/sudo
  79. # DEBUGGING OPTION
  80. # This option determines whether or not debugging messages are logged to the
  81. # syslog facility.
  82. # Values: 0=debugging off, 1=debugging on
  83. debug=0
  84. # COMMAND TIMEOUT
  85. # This specifies the maximum number of seconds that the NRPE daemon will
  86. # allow plugins to finish executing before killing them off.
  87. command_timeout=60
  88. # CONNECTION TIMEOUT
  89. # This specifies the maximum number of seconds that the NRPE daemon will
  90. # wait for a connection to be established before exiting. This is sometimes
  91. # seen where a network problem stops the SSL being established even though
  92. # all network sessions are connected. This causes the nrpe daemons to
  93. # accumulate, eating system resources. Do not set this too low.
  94. connection_timeout=300
  95. # WEEK RANDOM SEED OPTION
  96. # This directive allows you to use SSL even if your system does not have
  97. # a /dev/random or /dev/urandom (on purpose or because the necessary patches
  98. # were not applied). The random number generator will be seeded from a file
  99. # which is either a file pointed to by the environment valiable $RANDFILE
  100. # or $HOME/.rnd. If neither exists, the pseudo random number generator will
  101. # be initialized and a warning will be issued.
  102. # Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness
  103. #allow_weak_random_seed=1
  104. # INCLUDE CONFIG FILE
  105. # This directive allows you to include definitions from an external config file.
  106. #include=<somefile.cfg>
  107. # INCLUDE CONFIG DIRECTORY
  108. # This directive allows you to include definitions from config files (with a
  109. # .cfg extension) in one or more directories (with recursion).
  110. #include_dir=<somedirectory>
  111. #include_dir=<someotherdirectory>
  112. # COMMAND DEFINITIONS
  113. # Command definitions that this daemon will run. Definitions
  114. # are in the following format:
  115. #
  116. # command[<command_name>]=<command_line>
  117. #
  118. # When the daemon receives a request to return the results of <command_name>
  119. # it will execute the command specified by the <command_line> argument.
  120. #
  121. # Unlike Nagios, the command line cannot contain macros - it must be
  122. # typed exactly as it should be executed.
  123. #
  124. # Note: Any plugins that are used in the command lines must reside
  125. # on the machine that this daemon is running on! The examples below
  126. # assume that you have plugins installed in a /usr/local/nagios/libexec
  127. # directory. Also note that you will have to modify the definitions below
  128. # to match the argument format the plugins expect. Remember, these are
  129. # examples only!
  130. # The following examples use hardcoded command arguments...
  131. command[check_users]=@libexecdir@/check_users -w 5 -c 10
  132. command[check_load]=@libexecdir@/check_load -w 15,10,5 -c 30,25,20
  133. command[check_disk1]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hda1
  134. command[check_disk2]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hdb1
  135. command[check_zombie_procs]=@libexecdir@/check_procs -w 5 -c 10 -s Z
  136. command[check_total_procs]=@libexecdir@/check_procs -w 150 -c 200
  137. # The following examples allow user-supplied arguments and can
  138. # only be used if the NRPE daemon was compiled with support for
  139. # command arguments *AND* the dont_blame_nrpe directive in this
  140. # config file is set to '1'...
  141. #command[check_users]=@libexecdir@/check_users -w $ARG1$ -c $ARG2$
  142. #command[check_load]=@libexecdir@/check_load -w $ARG1$ -c $ARG2$
  143. #command[check_disk]=@libexecdir@/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
  144. #command[check_procs]=@libexecdir@/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$