<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style>  </head> <body lang=FR link=blue vlink=purple> <div class=Section1> Hello,<o:p></o:p> <o:p> </o:p> I’am triyng to have this king of notification :<o:p></o:p> <o:p> </o:p> <o:p> </o:p> define command{<o:p></o:p> command_name host-par-snmptrap<o:p></o:p> command_line /usr/bin/snmptrap -v 1 -c public 194.2.53.41 1.3.6.1.4.1.999 $HOSTADDRESS$ 6 0 '' .0.15.1 s "$HOSTGROUPALIAS$ $HOSTGROU<o:p></o:p> PNAME$ <st1:place w:st="on">PING</st1:place> $HOSTSTATE$ `/bin/echo "$HOSTOUTPUT$" | /bin/sed "s/\ /\_/g"`"<o:p></o:p> }<o:p></o:p> <o:p> </o:p> define command{<o:p></o:p> command_name service-par-snmptrap<o:p></o:p> command_line /usr/bin/snmptrap -v 1 -c public 194.2.53.41 1.3.6.1.4.1.999 $HOSTADDRESS$ 6 0 '' .0.15.1 s "$HOSTGROUPALIAS$ $HOSTGROU<o:p></o:p> P$ $SERVICEDESC$ $SERVICESTATE$ `/bin/echo "$SERVICEOUTPUT$" | /bin/sed "s/\ /\_/g"`"<o:p></o:p> }<o:p></o:p> <o:p> </o:p> But nothing append , I never receive any notification … <o:p></o:p> <o:p> </o:p> Does someone have an idea ??? <o:p></o:p> <o:p> </o:p> My nagios.cfg :<o:p></o:p> <o:p> </o:p> ##############################################################################<o:p></o:p> #<o:p></o:p> # NAGIOS.CFG - Sample Main Config File for Nagios 2.8<o:p></o:p> #<o:p></o:p> # Read the documentation for more information on this configuration<o:p></o:p> # file. I've provided some comments here, but things may not be so<o:p></o:p> # clear without further explanation.<o:p></o:p> #<o:p></o:p> # Last Modified: 12-21-2006<o:p></o:p> #<o:p></o:p> ##############################################################################<o:p></o:p> <o:p> </o:p> <o:p> </o:p> # LOG FILE<o:p></o:p> # This is the main log file where service and host events are logged<o:p></o:p> # for historical purposes. This should be the first option specified <o:p></o:p> # in the config file!!!<o:p></o:p> <o:p> </o:p> log_file=/usr/local/nagios/var/nagios.log<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # OBJECT CONFIGURATION FILE(S)<o:p></o:p> # This is the configuration file in which you define hosts, host<o:p></o:p> # groups, contacts, contact groups, services, etc. I guess it would<o:p></o:p> # be better called an object definition file, but for historical<o:p></o:p> # reasons it isn't. You can split object definitions into several<o:p></o:p> # different config files by using multiple cfg_file statements here.<o:p></o:p> # Nagios will read and process all the config files you define.<o:p></o:p> # This can be very useful if you want to keep command definitions <o:p></o:p> # separate from host and contact definitions...<o:p></o:p> <o:p> </o:p> # Command definitions<o:p></o:p> <o:p> </o:p> # Host and service definitions for monitoring this machine<o:p></o:p> <o:p> </o:p> <o:p> </o:p> # You can split other types of object definitions across several<o:p></o:p> # config files if you wish (as done here), or keep them all in a<o:p></o:p> # single config file.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> cfg_file=/usr/local/nagios/etc/hosts.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/services.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/misccommands.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/checkcommands.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/contactgroups.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/contacts.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/hostgroups.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/servicegroups.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/timeperiods.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/escalations.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/dependencies.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/hostextinfo.cfg<o:p></o:p> cfg_file=/usr/local/nagios/etc/serviceextinfo.cfg<o:p></o:p> resource_file=/usr/local/nagios/etc/resource.cfg<o:p></o:p> <o:p> </o:p> # OBJECT CACHE FILE<o:p></o:p> # This option determines where object definitions are cached when<o:p></o:p> # Nagios starts/restarts. The CGIs read object definitions from <o:p></o:p> # this cache file (rather than looking at the object config files<o:p></o:p> # directly) in order to prevent inconsistencies that can occur<o:p></o:p> # when the config files are modified after Nagios starts.<o:p></o:p> <o:p> </o:p> object_cache_file=/usr/local/nagios/var/objects.cache<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # RESOURCE FILE<o:p></o:p> # This is an optional resource file that contains $USERx$ macro<o:p></o:p> # definitions. Multiple resource files can be specified by using<o:p></o:p> # multiple resource_file definitions. The CGIs will not attempt to<o:p></o:p> # read the contents of resource files, so information that is<o:p></o:p> # considered to be sensitive (usernames, passwords, etc) can be<o:p></o:p> # defined as macros in this file and restrictive permissions (600)<o:p></o:p> # can be placed on this file.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # STATUS FILE<o:p></o:p> # This is where the current status of all monitored services and<o:p></o:p> # hosts is stored. Its contents are read and processed by the CGIs.<o:p></o:p> # The contents of the status file are deleted every time Nagios<o:p></o:p> # restarts.<o:p></o:p> <o:p> </o:p> status_file=/usr/local/nagios/var/status.dat<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # NAGIOS USER<o:p></o:p> # This determines the effective user that Nagios should run as. <o:p></o:p> # You can either supply a username or a UID.<o:p></o:p> <o:p> </o:p> nagios_user=nagios<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # NAGIOS GROUP<o:p></o:p> # This determines the effective group that Nagios should run as. <o:p></o:p> # You can either supply a group name or a GID.<o:p></o:p> <o:p> </o:p> nagios_group=nagios<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EXTERNAL COMMAND OPTION<o:p></o:p> # This option allows you to specify whether or not Nagios should check<o:p></o:p> # for external commands (in the command file defined below). By default<o:p></o:p> # Nagios will *not* check for external commands, just to be on the<o:p></o:p> # cautious side. If you want to be able to use the CGI command interface<o:p></o:p> # you will have to enable this. Setting this value to 0 disables command<o:p></o:p> # checking (the default), other values enable it.<o:p></o:p> <o:p> </o:p> check_external_commands=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EXTERNAL COMMAND CHECK INTERVAL<o:p></o:p> # This is the interval at which Nagios should check for external commands.<o:p></o:p> # This value works of the interval_length you specify later. If you leave<o:p></o:p> # that at its default value of 60 (seconds), a value of 1 here will cause<o:p></o:p> # Nagios to check for external commands every minute. If you specify a<o:p></o:p> # number followed by an "s" (i.e. 15s), this will be interpreted to mean<o:p></o:p> # actual seconds rather than a multiple of the interval_length variable.<o:p></o:p> # Note: In addition to reading the external command file at regularly <o:p></o:p> # scheduled intervals, Nagios will also check for external commands after<o:p></o:p> # event handlers are executed.<o:p></o:p> # NOTE: Setting this value to -1 causes Nagios to check the external<o:p></o:p> # command file as often as possible.<o:p></o:p> <o:p> </o:p> #command_check_interval=15s<o:p></o:p> command_check_interval=15s<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EXTERNAL COMMAND FILE<o:p></o:p> # This is the file that Nagios checks for external command requests.<o:p></o:p> # It is also where the command CGI will write commands that are submitted<o:p></o:p> # by users, so it must be writeable by the user that the web server<o:p></o:p> # is running as (usually 'nobody'). Permissions should be set at the <o:p></o:p> # directory level instead of on the file, as the file is deleted every<o:p></o:p> # time its contents are processed.<o:p></o:p> <o:p> </o:p> command_file=/usr/local/nagios/var/rw/nagios.cmd<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EXTERNAL COMMAND BUFFER SLOTS<o:p></o:p> # This settings is used to tweak the number of items or "slots" that<o:p></o:p> # the Nagios daemon should allocate to the buffer that holds incoming <o:p></o:p> # external commands before they are processed. As external commands <o:p></o:p> # are processed by the daemon, they are removed from the buffer. <o:p></o:p> <o:p> </o:p> external_command_buffer_slots=4096<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # COMMENT FILE<o:p></o:p> # This is the file that Nagios will use for storing host and service<o:p></o:p> # comments.<o:p></o:p> <o:p> </o:p> comment_file=/usr/local/nagios/var/comments.dat<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # DOWNTIME FILE<o:p></o:p> # This is the file that Nagios will use for storing host and service<o:p></o:p> # downtime data.<o:p></o:p> <o:p> </o:p> downtime_file=/usr/local/nagios/var/downtime.dat<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # LOCK FILE<o:p></o:p> # This is the lockfile that Nagios will use to store its PID number<o:p></o:p> # in when it is running in daemon mode.<o:p></o:p> <o:p> </o:p> lock_file=/usr/local/nagios/var/nagios.lock<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # TEMP FILE<o:p></o:p> # This is a temporary file that is used as scratch space when Nagios<o:p></o:p> # updates the status log, cleans the comment file, etc. This file<o:p></o:p> # is created, used, and deleted throughout the time that Nagios is<o:p></o:p> # running.<o:p></o:p> <o:p> </o:p> temp_file=/usr/local/nagios/var/nagios.tmp<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EVENT BROKER OPTIONS<o:p></o:p> # Controls what (if any) data gets sent to the event broker.<o:p></o:p> # Values: 0 = Broker nothing<o:p></o:p> # -1 = Broker everything<o:p></o:p> # <other> = See documentation<o:p></o:p> <o:p> </o:p> event_broker_options=-1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EVENT BROKER MODULE(S)<o:p></o:p> # This directive is used to specify an event broker module that should<o:p></o:p> # by loaded by Nagios at startup. Use multiple directives if you want<o:p></o:p> # to load more than one module. Arguments that should be passed to<o:p></o:p> # the module at startup are seperated from the module path by a space.<o:p></o:p> #<o:p></o:p> # Example:<o:p></o:p> #<o:p></o:p> # broker_module=<modulepath> [moduleargs]<o:p></o:p> <o:p> </o:p> #broker_module=/somewhere/module1.o<o:p></o:p> #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # LOG ROTATION METHOD<o:p></o:p> # This is the log rotation method that Nagios should use to rotate<o:p></o:p> # the main log file. Values are as follows..<o:p></o:p> # n = None - don't rotate the log<o:p></o:p> # h = Hourly rotation (top of the hour)<o:p></o:p> # d = Daily rotation (midnight every day)<o:p></o:p> # w = Weekly rotation (midnight on Saturday evening)<o:p></o:p> # m = Monthly rotation (midnight last day of month)<o:p></o:p> <o:p> </o:p> log_rotation_method=d<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # LOG ARCHIVE PATH<o:p></o:p> # This is the directory where archived (rotated) log files should be <o:p></o:p> # placed (assuming you've chosen to do log rotation).<o:p></o:p> <o:p> </o:p> log_archive_path=/usr/local/nagios/var/archives<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # LOGGING OPTIONS<o:p></o:p> # If you want messages logged to the syslog facility, as well as the<o:p></o:p> # NetAlarm log file set this option to 1. If not, set it to 0.<o:p></o:p> <o:p> </o:p> use_syslog=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # NOTIFICATION LOGGING OPTION<o:p></o:p> # If you don't want notifications to be logged, set this value to 0.<o:p></o:p> # If notifications should be logged, set the value to 1.<o:p></o:p> <o:p> </o:p> log_notifications=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE RETRY LOGGING OPTION<o:p></o:p> # If you don't want service check retries to be logged, set this value<o:p></o:p> # to 0. If retries should be logged, set the value to 1.<o:p></o:p> <o:p> </o:p> log_service_retries=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST RETRY LOGGING OPTION<o:p></o:p> # If you don't want host check retries to be logged, set this value to<o:p></o:p> # 0. If retries should be logged, set the value to 1.<o:p></o:p> <o:p> </o:p> log_host_retries=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EVENT HANDLER LOGGING OPTION<o:p></o:p> # If you don't want host and service event handlers to be logged, set<o:p></o:p> # this value to 0. If event handlers should be logged, set the value<o:p></o:p> # to 1.<o:p></o:p> <o:p> </o:p> log_event_handlers=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # INITIAL STATES LOGGING OPTION<o:p></o:p> # If you want Nagios to log all initial host and service states to<o:p></o:p> # the main log file (the first time the service or host is checked)<o:p></o:p> # you can enable this option by setting this value to 1. If you<o:p></o:p> # are not using an external application that does long term state<o:p></o:p> # statistics reporting, you do not need to enable this option. In<o:p></o:p> # this case, set the value to 0.<o:p></o:p> <o:p> </o:p> log_initial_states=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EXTERNAL COMMANDS LOGGING OPTION<o:p></o:p> # If you don't want Nagios to log external commands, set this value<o:p></o:p> # to 0. If external commands should be logged, set this value to 1.<o:p></o:p> # Note: This option does not include logging of passive service<o:p></o:p> # checks - see the option below for controlling whether or not<o:p></o:p> # passive checks are logged.<o:p></o:p> <o:p> </o:p> log_external_commands=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # PASSIVE CHECKS LOGGING OPTION<o:p></o:p> # If you don't want Nagios to log passive host and service checks, set<o:p></o:p> # this value to 0. If passive checks should be logged, set<o:p></o:p> # this value to 1.<o:p></o:p> <o:p> </o:p> log_passive_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # GLOBAL HOST AND SERVICE EVENT HANDLERS<o:p></o:p> # These options allow you to specify a host and service event handler<o:p></o:p> # command that is to be run for every host or service state change.<o:p></o:p> # The global event handler is executed immediately prior to the event<o:p></o:p> # handler that you have optionally specified in each host or<o:p></o:p> # service definition. The command argument is the short name of a<o:p></o:p> # command definition that you define in your host configuration file.<o:p></o:p> # Read the HTML docs for more information.<o:p></o:p> <o:p> </o:p> #global_host_event_handler=somecommand<o:p></o:p> #global_service_event_handler=somecommand<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE INTER-CHECK DELAY METHOD<o:p></o:p> # This is the method that Nagios should use when initially<o:p></o:p> # "spreading out" service checks when it starts monitoring. The<o:p></o:p> # default is to use smart delay calculation, which will try to<o:p></o:p> # space all service checks out evenly to minimize CPU load.<o:p></o:p> # Using the dumb setting will cause all checks to be scheduled<o:p></o:p> # at the same time (with no delay between them)! This is not a<o:p></o:p> # good thing for production, but is useful when testing the<o:p></o:p> # parallelization functionality.<o:p></o:p> # n = None - don't use any delay between checks<o:p></o:p> # d = Use a "dumb" delay of 1 second between checks<o:p></o:p> # s = Use "smart" inter-check delay calculation<o:p></o:p> # x.xx = Use an inter-check delay of x.xx seconds<o:p></o:p> <o:p> </o:p> service_inter_check_delay_method=s<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # MAXIMUM SERVICE CHECK SPREAD<o:p></o:p> # This variable determines the timeframe (in minutes) from the<o:p></o:p> # program start time that an initial check of all services should<o:p></o:p> # be completed. Default is 30 minutes.<o:p></o:p> <o:p> </o:p> max_service_check_spread=30<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE CHECK INTERLEAVE FACTOR<o:p></o:p> # This variable determines how service checks are interleaved.<o:p></o:p> # Interleaving the service checks allows for a more even<o:p></o:p> # distribution of service checks and reduced load on remote<o:p></o:p> # hosts. Setting this value to 1 is equivalent to how versions<o:p></o:p> # of Nagios previous to 0.0.5 did service checks. Set this<o:p></o:p> # value to s (smart) for automatic calculation of the interleave<o:p></o:p> # factor unless you have a specific reason to change it.<o:p></o:p> # s = Use "smart" interleave factor calculation<o:p></o:p> # x = Use an interleave factor of x, where x is a<o:p></o:p> # number greater than or equal to 1.<o:p></o:p> <o:p> </o:p> service_interleave_factor=s<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST INTER-CHECK DELAY METHOD<o:p></o:p> # This is the method that Nagios should use when initially<o:p></o:p> # "spreading out" host checks when it starts monitoring. The<o:p></o:p> # default is to use smart delay calculation, which will try to<o:p></o:p> # space all host checks out evenly to minimize CPU load.<o:p></o:p> # Using the dumb setting will cause all checks to be scheduled<o:p></o:p> # at the same time (with no delay between them)!<o:p></o:p> # n = None - don't use any delay between checks<o:p></o:p> # d = Use a "dumb" delay of 1 second between checks<o:p></o:p> # s = Use "smart" inter-check delay calculation<o:p></o:p> # x.xx = Use an inter-check delay of x.xx seconds<o:p></o:p> <o:p> </o:p> host_inter_check_delay_method=s<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # MAXIMUM HOST CHECK SPREAD<o:p></o:p> # This variable determines the timeframe (in minutes) from the<o:p></o:p> # program start time that an initial check of all hosts should<o:p></o:p> # be completed. Default is 30 minutes.<o:p></o:p> <o:p> </o:p> max_host_check_spread=30<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # MAXIMUM CONCURRENT SERVICE CHECKS<o:p></o:p> # This option allows you to specify the maximum number of <o:p></o:p> # service checks that can be run in parallel at any given time.<o:p></o:p> # Specifying a value of 1 for this variable essentially prevents<o:p></o:p> # any service checks from being parallelized. A value of 0<o:p></o:p> # will not restrict the number of concurrent checks that are<o:p></o:p> # being executed.<o:p></o:p> <o:p> </o:p> max_concurrent_checks=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE CHECK REAPER FREQUENCY<o:p></o:p> # This is the frequency (in seconds!) that Nagios will process<o:p></o:p> # the results of services that have been checked.<o:p></o:p> <o:p> </o:p> service_reaper_frequency=10<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # CHECK RESULT BUFFER SLOTS<o:p></o:p> # This settings is used to tweak the number of items or "slots" that<o:p></o:p> # the Nagios daemon should allocate to the buffer that holds <o:p></o:p> # service check results before they are processed. As check results<o:p></o:p> # are processed by the daemon, they are removed from the buffer. <o:p></o:p> <o:p> </o:p> check_result_buffer_slots=4096<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AUTO-RESCHEDULING OPTION<o:p></o:p> # This option determines whether or not Nagios will attempt to<o:p></o:p> # automatically reschedule active host and service checks to<o:p></o:p> # "smooth" them out over time. This can help balance the load on<o:p></o:p> # the monitoring server. <o:p></o:p> # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE<o:p></o:p> # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY<o:p></o:p> <o:p> </o:p> auto_reschedule_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AUTO-RESCHEDULING INTERVAL<o:p></o:p> # This option determines how often (in seconds) Nagios will<o:p></o:p> # attempt to automatically reschedule checks. This option only<o:p></o:p> # has an effect if the auto_reschedule_checks option is enabled.<o:p></o:p> # Default is 30 seconds.<o:p></o:p> # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE<o:p></o:p> # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY<o:p></o:p> <o:p> </o:p> auto_rescheduling_interval=30<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AUTO-RESCHEDULING WINDOW<o:p></o:p> # This option determines the "window" of time (in seconds) that<o:p></o:p> # Nagios will look at when automatically rescheduling checks.<o:p></o:p> # Only host and service checks that occur in the next X seconds<o:p></o:p> # (determined by this variable) will be rescheduled. This option<o:p></o:p> # only has an effect if the auto_reschedule_checks option is<o:p></o:p> # enabled. Default is 180 seconds (3 minutes).<o:p></o:p> # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE<o:p></o:p> # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY<o:p></o:p> <o:p> </o:p> auto_rescheduling_window=180<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SLEEP TIME<o:p></o:p> # This is the number of seconds to sleep between checking for system<o:p></o:p> # events and service checks that need to be run.<o:p></o:p> <o:p> </o:p> sleep_time=0.25<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # TIMEOUT VALUES<o:p></o:p> # These options control how much time Nagios will allow various<o:p></o:p> # types of commands to execute before killing them off. Options<o:p></o:p> # are available for controlling maximum time allotted for<o:p></o:p> # service checks, host checks, event handlers, notifications, the<o:p></o:p> # ocsp command, and performance data commands. All values are in<o:p></o:p> # seconds.<o:p></o:p> <o:p> </o:p> service_check_timeout=60<o:p></o:p> host_check_timeout=30<o:p></o:p> event_handler_timeout=30<o:p></o:p> notification_timeout=30<o:p></o:p> ocsp_timeout=5<o:p></o:p> perfdata_timeout=5<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # RETAIN STATE INFORMATION<o:p></o:p> # This setting determines whether or not Nagios will save state<o:p></o:p> # information for services and hosts before it shuts down. Upon<o:p></o:p> # startup Nagios will reload all saved service and host state<o:p></o:p> # information before starting to monitor. This is useful for <o:p></o:p> # maintaining long-term data on state statistics, etc, but will<o:p></o:p> # slow Nagios down a bit when it (re)starts. Since its only<o:p></o:p> # a one-time penalty, I think its well worth the additional<o:p></o:p> # startup delay.<o:p></o:p> <o:p> </o:p> retain_state_information=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # STATE RETENTION FILE<o:p></o:p> # This is the file that Nagios should use to store host and<o:p></o:p> # service state information before it shuts down. The state <o:p></o:p> # information in this file is also read immediately prior to<o:p></o:p> # starting to monitor the network when Nagios is restarted.<o:p></o:p> # This file is used only if the preserve_state_information<o:p></o:p> # variable is set to 1.<o:p></o:p> <o:p> </o:p> state_retention_file=/usr/local/nagios/var/retention.dat<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # RETENTION DATA UPDATE INTERVAL<o:p></o:p> # This setting determines how often (in minutes) that Nagios<o:p></o:p> # will automatically save retention data during normal operation.<o:p></o:p> # If you set this value to 0, Nagios will not save retention<o:p></o:p> # data at regular interval, but it will still save retention<o:p></o:p> # data before shutting down or restarting. If you have disabled<o:p></o:p> # state retention, this option has no effect.<o:p></o:p> <o:p> </o:p> retention_update_interval=60<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # USE RETAINED <st1:place w:st="on"><st1:PlaceName w:st="on">PROGRAM</st1:PlaceName> <st1:PlaceType w:st="on">STATE</st1:PlaceType></st1:place><o:p></o:p> # This setting determines whether or not Nagios will set <o:p></o:p> # program status variables based on the values saved in the<o:p></o:p> # retention file. If you want to use retained program status<o:p></o:p> # information, set this value to 1. If not, set this value<o:p></o:p> # to 0.<o:p></o:p> <o:p> </o:p> use_retained_program_state=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # USE RETAINED SCHEDULING INFO<o:p></o:p> # This setting determines whether or not Nagios will retain<o:p></o:p> # the scheduling info (next check time) for hosts and services<o:p></o:p> # based on the values saved in the retention file. If you<o:p></o:p> # If you want to use retained scheduling info, set this<o:p></o:p> # value to 1. If not, set this value to 0.<o:p></o:p> <o:p> </o:p> use_retained_scheduling_info=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # INTERVAL LENGTH<o:p></o:p> # This is the seconds per unit interval as used in the<o:p></o:p> # host/contact/service configuration files. Setting this to 60 means<o:p></o:p> # that each interval is one minute long (60 seconds). Other settings<o:p></o:p> # have not been tested much, so your mileage is likely to vary...<o:p></o:p> <o:p> </o:p> interval_length=60<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AGGRESSIVE HOST CHECKING OPTION<o:p></o:p> # If you don't want to turn on aggressive host checking features, set<o:p></o:p> # this value to 0 (the default). Otherwise set this value to 1 to<o:p></o:p> # enable the aggressive check option. Read the docs for more info<o:p></o:p> # on what aggressive host check is or check out the source code in<o:p></o:p> # base/checks.c<o:p></o:p> <o:p> </o:p> use_aggressive_host_checking=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE CHECK EXECUTION OPTION<o:p></o:p> # This determines whether or not Nagios will actively execute<o:p></o:p> # service checks when it initially starts. If this option is <o:p></o:p> # disabled, checks are not actively made, but Nagios can still<o:p></o:p> # receive and process passive check results that come in. Unless<o:p></o:p> # you're implementing redundant hosts or have a special need for<o:p></o:p> # disabling the execution of service checks, leave this enabled!<o:p></o:p> # Values: 1 = enable checks, 0 = disable checks<o:p></o:p> <o:p> </o:p> execute_service_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # PASSIVE SERVICE CHECK ACCEPTANCE OPTION<o:p></o:p> # This determines whether or not Nagios will accept passive<o:p></o:p> # service checks results when it initially (re)starts.<o:p></o:p> # Values: 1 = accept passive checks, 0 = reject passive checks<o:p></o:p> <o:p> </o:p> accept_passive_service_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST CHECK EXECUTION OPTION<o:p></o:p> # This determines whether or not Nagios will actively execute<o:p></o:p> # host checks when it initially starts. If this option is <o:p></o:p> # disabled, checks are not actively made, but Nagios can still<o:p></o:p> # receive and process passive check results that come in. Unless<o:p></o:p> # you're implementing redundant hosts or have a special need for<o:p></o:p> # disabling the execution of host checks, leave this enabled!<o:p></o:p> # Values: 1 = enable checks, 0 = disable checks<o:p></o:p> <o:p> </o:p> execute_host_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # PASSIVE HOST CHECK ACCEPTANCE OPTION<o:p></o:p> # This determines whether or not Nagios will accept passive<o:p></o:p> # host checks results when it initially (re)starts.<o:p></o:p> # Values: 1 = accept passive checks, 0 = reject passive checks<o:p></o:p> <o:p> </o:p> accept_passive_host_checks=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # NOTIFICATIONS OPTION<o:p></o:p> # This determines whether or not Nagios will sent out any host or<o:p></o:p> # service notifications when it is initially (re)started.<o:p></o:p> # Values: 1 = enable notifications, 0 = disable notifications<o:p></o:p> <o:p> </o:p> enable_notifications=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # EVENT HANDLER USE OPTION<o:p></o:p> # This determines whether or not Nagios will run any host or<o:p></o:p> # service event handlers when it is initially (re)started. Unless<o:p></o:p> # you're implementing redundant hosts, leave this option enabled.<o:p></o:p> # Values: 1 = enable event handlers, 0 = disable event handlers<o:p></o:p> <o:p> </o:p> enable_event_handlers=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # PROCESS PERFORMANCE DATA OPTION<o:p></o:p> # This determines whether or not Nagios will process performance<o:p></o:p> # data returned from service and host checks. If this option is<o:p></o:p> # enabled, host performance data will be processed using the<o:p></o:p> # host_perfdata_command (defined below) and service performance<o:p></o:p> # data will be processed using the service_perfdata_command (also<o:p></o:p> # defined below). Read the HTML docs for more information on<o:p></o:p> # performance data.<o:p></o:p> # Values: 1 = process performance data, 0 = do not process performance data<o:p></o:p> <o:p> </o:p> process_performance_data=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS<o:p></o:p> # These commands are run after every host and service check is<o:p></o:p> # performed. These commands are executed only if the<o:p></o:p> # enable_performance_data option (above) is set to 1. The command<o:p></o:p> # argument is the short name of a command definition that you <o:p></o:p> # define in your host configuration file. Read the HTML docs for<o:p></o:p> # more information on performance data.<o:p></o:p> <o:p> </o:p> #host_perfdata_command=process-host-perfdata<o:p></o:p> #service_perfdata_command=process-service-perfdata<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA FILES<o:p></o:p> # These files are used to store host and service performance data.<o:p></o:p> # Performance data is only written to these files if the<o:p></o:p> # enable_performance_data option (above) is set to 1.<o:p></o:p> <o:p> </o:p> #host_perfdata_file=/tmp/host-perfdata<o:p></o:p> #service_perfdata_file=/tmp/service-perfdata<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES<o:p></o:p> # These options determine what data is written (and how) to the<o:p></o:p> # performance data files. The templates may contain macros, special<o:p></o:p> # characters (\t for tab, \r for carriage return, \n for newline)<o:p></o:p> # and plain text. A newline is automatically added after each write<o:p></o:p> # to the performance data file. Some examples of what you can do are<o:p></o:p> # shown below.<o:p></o:p> <o:p> </o:p> #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$<o:p></o:p> #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA FILE MODES<o:p></o:p> # This option determines whether or not the host and service<o:p></o:p> # performance data files are opened in write ("w") or append ("a")<o:p></o:p> # mode. Unless you are the files are named pipes, you will probably<o:p></o:p> # want to use the default mode of append ("a").<o:p></o:p> <o:p> </o:p> #host_perfdata_file_mode=a<o:p></o:p> #service_perfdata_file_mode=a<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL<o:p></o:p> # These options determine how often (in seconds) the host and service<o:p></o:p> # performance data files are processed using the commands defined<o:p></o:p> # below. A value of 0 indicates the files should not be periodically<o:p></o:p> # processed.<o:p></o:p> <o:p> </o:p> #host_perfdata_file_processing_interval=0<o:p></o:p> #service_perfdata_file_processing_interval=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS<o:p></o:p> # These commands are used to periodically process the host and<o:p></o:p> # service performance data files. The interval at which the<o:p></o:p> # processing occurs is determined by the options above.<o:p></o:p> <o:p> </o:p> #host_perfdata_file_processing_command=process-host-perfdata-file<o:p></o:p> #service_perfdata_file_processing_command=process-service-perfdata-file<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # OBSESS OVER SERVICE CHECKS OPTION<o:p></o:p> # This determines whether or not Nagios will obsess over service<o:p></o:p> # checks and run the ocsp_command defined below. Unless you're<o:p></o:p> # planning on implementing distributed monitoring, do not enable<o:p></o:p> # this option. Read the HTML docs for more information on<o:p></o:p> # implementing distributed monitoring.<o:p></o:p> # Values: 1 = obsess over services, 0 = do not obsess (default)<o:p></o:p> <o:p> </o:p> obsess_over_services=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND<o:p></o:p> # This is the command that is run for every service check that is<o:p></o:p> # processed by Nagios. This command is executed only if the<o:p></o:p> # obsess_over_service option (above) is set to 1. The command <o:p></o:p> # argument is the short name of a command definition that you<o:p></o:p> # define in your host configuration file. Read the HTML docs for<o:p></o:p> # more information on implementing distributed monitoring.<o:p></o:p> <o:p> </o:p> #ocsp_command=somecommand<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # ORPHANED SERVICE CHECK OPTION<o:p></o:p> # This determines whether or not Nagios will periodically <o:p></o:p> # check for orphaned services. Since service checks are not<o:p></o:p> # rescheduled until the results of their previous execution <o:p></o:p> # instance are processed, there exists a possibility that some<o:p></o:p> # checks may never get rescheduled. This seems to be a rare<o:p></o:p> # problem and should not happen under normal circumstances.<o:p></o:p> # If you have problems with service checks never getting<o:p></o:p> # rescheduled, you might want to try enabling this option.<o:p></o:p> # Values: 1 = enable checks, 0 = disable checks<o:p></o:p> <o:p> </o:p> check_for_orphaned_services=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE FRESHNESS CHECK OPTION<o:p></o:p> # This option determines whether or not Nagios will periodically<o:p></o:p> # check the "freshness" of service results. Enabling this option<o:p></o:p> # is useful for ensuring passive checks are received in a timely<o:p></o:p> # manner.<o:p></o:p> # Values: 1 = enabled freshness checking, 0 = disable freshness checking<o:p></o:p> <o:p> </o:p> check_service_freshness=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # SERVICE FRESHNESS CHECK INTERVAL<o:p></o:p> # This setting determines how often (in seconds) Nagios will<o:p></o:p> # check the "freshness" of service check results. If you have<o:p></o:p> # disabled service freshness checking, this option has no effect.<o:p></o:p> <o:p> </o:p> service_freshness_check_interval=60<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST FRESHNESS CHECK OPTION<o:p></o:p> # This option determines whether or not Nagios will periodically<o:p></o:p> # check the "freshness" of host results. Enabling this option<o:p></o:p> # is useful for ensuring passive checks are received in a timely<o:p></o:p> # manner.<o:p></o:p> # Values: 1 = enabled freshness checking, 0 = disable freshness checking<o:p></o:p> <o:p> </o:p> check_host_freshness=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # HOST FRESHNESS CHECK INTERVAL<o:p></o:p> # This setting determines how often (in seconds) Nagios will<o:p></o:p> # check the "freshness" of host check results. If you have<o:p></o:p> # disabled host freshness checking, this option has no effect.<o:p></o:p> <o:p> </o:p> host_freshness_check_interval=60<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AGGREGATED STATUS UPDATES<o:p></o:p> # This option determines whether or not Nagios will <o:p></o:p> # aggregate updates of host, service, and program status<o:p></o:p> # data. Normally, status data is updated immediately when<o:p></o:p> # a change occurs. This can result in high CPU loads if<o:p></o:p> # you are monitoring a lot of services. If you want Nagios<o:p></o:p> # to only refresh status data every few seconds, disable<o:p></o:p> # this option.<o:p></o:p> # Values: 1 = enable aggregate updates, 0 = disable aggregate updates<o:p></o:p> <o:p> </o:p> aggregate_status_updates=1<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # AGGREGATED STATUS UPDATE INTERVAL<o:p></o:p> # Combined with the aggregate_status_updates option,<o:p></o:p> # this option determines the frequency (in seconds!) that<o:p></o:p> # Nagios will periodically dump program, host, and <o:p></o:p> # service status data. If you are not using aggregated<o:p></o:p> # status data updates, this option has no effect.<o:p></o:p> <o:p> </o:p> status_update_interval=15<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # FLAP DETECTION OPTION<o:p></o:p> # This option determines whether or not Nagios will try<o:p></o:p> # and detect hosts and services that are "flapping". <o:p></o:p> # Flapping occurs when a host or service changes between<o:p></o:p> # states too frequently. When Nagios detects that a <o:p></o:p> # host or service is flapping, it will temporarily suppress<o:p></o:p> # notifications for that host/service until it stops<o:p></o:p> # flapping. Flap detection is very experimental, so read<o:p></o:p> # the HTML documentation before enabling this feature!<o:p></o:p> # Values: 1 = enable flap detection<o:p></o:p> # 0 = disable flap detection (default)<o:p></o:p> <o:p> </o:p> enable_flap_detection=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES<o:p></o:p> # Read the HTML documentation on flap detection for<o:p></o:p> # an explanation of what this option does. This option<o:p></o:p> # has no effect if flap detection is disabled.<o:p></o:p> <o:p> </o:p> low_service_flap_threshold=5.0<o:p></o:p> high_service_flap_threshold=20.0<o:p></o:p> low_host_flap_threshold=5.0<o:p></o:p> high_host_flap_threshold=20.0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # DATE FORMAT OPTION<o:p></o:p> # This option determines how short dates are displayed. Valid options<o:p></o:p> # include:<o:p></o:p> # us (MM-DD-YYYY HH:MM:SS)<o:p></o:p> # euro (DD-MM-YYYY HH:MM:SS)<o:p></o:p> # iso8601 (YYYY-MM-DD HH:MM:SS)<o:p></o:p> # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)<o:p></o:p> #<o:p></o:p> <o:p> </o:p> date_format=us<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # P1.PL FILE LOCATION<o:p></o:p> # This value determines where the p1.pl perl script (used by the<o:p></o:p> # embedded Perl interpreter) is located. If you didn't compile<o:p></o:p> # Nagios with embedded Perl support, this option has no effect.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # ILLEGAL OBJECT NAME CHARACTERS<o:p></o:p> # This option allows you to specify illegal characters that cannot<o:p></o:p> # be used in host names, service descriptions, or names of other<o:p></o:p> # object types.<o:p></o:p> <o:p> </o:p> illegal_object_name_chars=`~!$%^&*|'"<>?,()=<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # ILLEGAL MACRO OUTPUT CHARACTERS<o:p></o:p> # This option allows you to specify illegal characters that are<o:p></o:p> # stripped from macros before being used in notifications, event<o:p></o:p> # handlers, etc. This DOES NOT affect macros used in service or<o:p></o:p> # host check commands.<o:p></o:p> # The following macros are stripped of the characters you specify:<o:p></o:p> # $HOSTOUTPUT$<o:p></o:p> # $HOSTPERFDATA$<o:p></o:p> # $HOSTACKAUTHOR$<o:p></o:p> # $HOSTACKCOMMENT$<o:p></o:p> # $SERVICEOUTPUT$<o:p></o:p> # $SERVICEPERFDATA$<o:p></o:p> # $SERVICEACKAUTHOR$<o:p></o:p> # $SERVICEACKCOMMENT$<o:p></o:p> <o:p> </o:p> illegal_macro_output_chars=`~$&|'"<><o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # REGULAR EXPRESSION MATCHING<o:p></o:p> # This option controls whether or not regular expression matching<o:p></o:p> # takes place in the object config files. Regular expression<o:p></o:p> # matching is used to match host, hostgroup, service, and service<o:p></o:p> # group names/descriptions in some fields of various object types.<o:p></o:p> # Values: 1 = enable regexp matching, 0 = disable regexp matching<o:p></o:p> <o:p> </o:p> use_regexp_matching=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # "TRUE" REGULAR EXPRESSION MATCHING<o:p></o:p> # This option controls whether or not "true" regular expression <o:p></o:p> # matching takes place in the object config files. This option<o:p></o:p> # only has an effect if regular expression matching is enabled<o:p></o:p> # (see above). If this option is DISABLED, regular expression<o:p></o:p> # matching only occurs if a string contains wildcard characters<o:p></o:p> # (* and ?). If the option is ENABLED, regexp matching occurs<o:p></o:p> # all the time (which can be annoying).<o:p></o:p> # Values: 1 = enable true matching, 0 = disable true matching<o:p></o:p> <o:p> </o:p> use_true_regexp_matching=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # ADMINISTRATOR EMAIL ADDRESS<o:p></o:p> # The email address of the administrator of *this* machine (the one<o:p></o:p> # doing the monitoring). Nagios never uses this value itself, but<o:p></o:p> # you can access this value by using the $ADMINEMAIL$ macro in your<o:p></o:p> # notification commands.<o:p></o:p> <o:p> </o:p> admin_email=nagios<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # ADMINISTRATOR PAGER NUMBER/ADDRESS<o:p></o:p> # The pager number/address for the administrator of *this* machine.<o:p></o:p> # Nagios never uses this value itself, but you can access this<o:p></o:p> # value by using the $ADMINPAGER$ macro in your notification<o:p></o:p> # commands.<o:p></o:p> <o:p> </o:p> admin_pager=pagenagios<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> # DAEMON CORE DUMP OPTION<o:p></o:p> # This option determines whether or not Nagios is allowed to create<o:p></o:p> # a core dump when it runs as a daemon. Note that it is generally<o:p></o:p> # considered bad form to allow this, but it may be useful for<o:p></o:p> # debugging purposes.<o:p></o:p> # Values: 1 - Allow core dumps<o:p></o:p> # 0 - Do not allow core dumps (default)<o:p></o:p> <o:p> </o:p> daemon_dumps_core=0<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Thanks <o:p></o:p> </div> </body> </html>