nrpe.cfg.in 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145
  1. #############################################################################
  2. # Sample NRPE Config File
  3. # Written by: Ethan Galstad (nagios@nagios.org)
  4. #
  5. # Last Modified: 01-20-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. # COMMAND ARGUMENT PROCESSING
  40. # This option determines whether or not the NRPE daemon will allow clients
  41. # to specify arguments to commands that are executed. This option only works
  42. # if the daemon was configured with the --enable-command-args configure script
  43. # option.
  44. #
  45. # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
  46. # Read the SECURITY file for information on some of the security implications
  47. # of enabling this variable.
  48. #
  49. # Values: 0=do not allow arguments, 1=allow command arguments
  50. dont_blame_nrpe=0
  51. # DEBUGGING OPTION
  52. # This option determines whether or not debugging messages are logged to the
  53. # syslog facility.
  54. # Values: 0=debugging off, 1=debugging on
  55. debug=0
  56. # COMMAND TIMEOUT
  57. # This specifies the maximum number of seconds that the NRPE daemon will
  58. # allow plugins to finish executing before killing them off.
  59. command_timeout=60
  60. # INCLUDE CONFIG FILE
  61. # This directive allows you to include definitions from an external config file.
  62. #include=<somefile.cfg>
  63. # INCLUDE CONFIG DIRECTORY
  64. # This directive allows you to include definitions from config files (with a
  65. # .cfg extension) in one or more directories (with recursion).
  66. #include_dir=<somedirectory>
  67. #include_dir=<someotherdirectory>
  68. # COMMAND DEFINITIONS
  69. # Command definitions that this daemon will run. Definitions
  70. # are in the following format:
  71. #
  72. # command[<command_name>]=<command_line>
  73. #
  74. # When the daemon receives a request to return the results of <command_name>
  75. # it will execute the command specified by the <command_line> argument.
  76. #
  77. # Unlike Nagios, the command line cannot contain macros - it must be
  78. # typed exactly as it should be executed.
  79. #
  80. # Note: Any plugins that are used in the command lines must reside
  81. # on the machine that this daemon is running on! The examples below
  82. # assume that you have plugins installed in a /usr/local/nagios/libexec
  83. # directory. Also note that you will have to modify the definitions below
  84. # to match the argument format the plugins expect. Remember, these are
  85. # examples only!
  86. # The following examples use hardcoded command arguments...
  87. command[check_users]=@libexecdir@/check_users -w 5 -c 10
  88. command[check_load]=@libexecdir@/check_load -w 15,10,5 -c 30,25,20
  89. command[check_disk1]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hda1
  90. command[check_disk2]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hdb1
  91. command[check_zombie_procs]=@libexecdir@/check_procs -w 5 -c 10 -s Z
  92. command[check_total_procs]=@libexecdir@/check_procs -w 150 -c 200
  93. # The following examples allow user-supplied arguments and can
  94. # only be used if the NRPE daemon was compiled with support for
  95. # command arguments *AND* the dont_blame_nrpe directive in this
  96. # config file is set to '1'...
  97. #command[check_users]=@libexecdir@/check_users -w $ARG1$ -c $ARG2$
  98. #command[check_load]=@libexecdir@/check_load -w $ARG1$ -c $ARG2$
  99. #command[check_disk]=@libexecdir@/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
  100. #command[check_procs]=@libexecdir@/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$