Thread: [Nagios-checkins] nagios/html/docs about.html, 1.6, 1.7 activechecks.html, 1.4, 1.5 adaptive.html,
Nagios network monitoring software is enterprise server monitoring
Brought to you by:
egalstad,
sawolf-nagios
Menu
▾
▴
nagios-checkins
Update of /cvsroot/nagios/nagios/html/docs In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv12768/html/docs Modified Files: about.html activechecks.html adaptive.html addons.html beginners.html cachedchecks.html cgiauth.html cgiincludes.html cgis.html checkscheduling.html clusters.html config.html configcgi.html configmain.html configobject.html customobjectvars.html dependencies.html dependencychecks.html distributed.html downtime.html embeddedperl.html epnplugins.html escalations.html eventhandlers.html extcommands.html faststartup.html flapping.html freshness.html funstuff.html hostchecks.html index.html int-snmptrap.html int-tcpwrappers.html integration.html largeinstalltweaks.html macrolist.html macros.html monitoring-linux.html monitoring-netware.html monitoring-printers.html monitoring-publicservices.html monitoring-routers.html monitoring-windows.html mrtggraphs.html nagiostats.html networkreachability.html notifications.html objectdefinitions.html objectinheritance.html objecttricks.html oncallrotation.html passivechecks.html passivestatetranslation.html perfdata.html pluginapi.html plugins.html quickstart-fedora.html quickstart-opensuse.html quickstart-ubuntu.html quickstart.html redundancy.html security.html servicechecks.html stalking.html startstop.html statetypes.html timeperiods.html toc.html tuning.html upgrading.html verifyconfig.html volatileservices.html whatsnew.html Log Message: HTML documentation cleanup: links, HTMLtidy, validity Index: objectdefinitions.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/objectdefinitions.html,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** objectdefinitions.html 30 Aug 2007 06:38:05 -0000 1.13 --- objectdefinitions.html 30 Aug 2007 22:35:08 -0000 1.14 *************** *** 24,33 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Object Definitions</h1> </div> - </p> <hr> [...1030 lines suppressed...] ! <p><div class="SectionTitle">Variable Descriptions:</div></p> ! <p> <table border="0" class="Default"> <tr> --- 1995,2000 ---- </pre> ! <p class="SectionTitle">Variable Descriptions:</p> ! <table border="0" class="Default"> <tr> *************** *** 2084,2088 **** </tr> </table> - </p> --- 2041,2044 ---- Index: cgiauth.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/cgiauth.html,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** cgiauth.html 30 Aug 2007 06:37:51 -0000 1.9 --- cgiauth.html 30 Aug 2007 22:35:04 -0000 1.10 *************** *** 1,2 **** --- 1,4 ---- + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> + <html> <head> *************** *** 14,23 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Authentication And Authorization In The CGIs</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 36,39 **** --- 36,45 ---- </p> + + <a name="definitions"></a> + <p> + <strong><u>Definitions</u></strong> + </p> + <p> Before continuing, it is important that you understand the meaning of and difference between authenticated users and authenticated contacts: *************** *** 90,94 **** </p> - <p> <table border="1" class="Default"> <tr bgcolor="#cbcbcb"> --- 96,99 ---- *************** *** 149,153 **** <tr> <td>All Configuration Information</td> ! <td>No</td></td> <td>No</td> </tr> --- 154,158 ---- <tr> <td>All Configuration Information</td> ! <td>No</td> <td>No</td> </tr> *************** *** 163,167 **** </tr> </table> ! </p> <p> --- 168,173 ---- </tr> </table> ! ! <br> <p> Index: monitoring-netware.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/monitoring-netware.html,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** monitoring-netware.html 30 Aug 2007 06:38:01 -0000 1.6 --- monitoring-netware.html 30 Aug 2007 22:35:07 -0000 1.7 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Monitoring Netware Servers</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 68,72 **** <p> ! Novell has various documentation on monitoring Netware servers with Nagios at their <a href="http://www.novell.com/coolsolutions">Cool Solutions</a>, including: </p> --- 66,70 ---- <p> ! Novell has various documentation on monitoring Netware servers with Nagios at their <a href="http://www.novell.com/coolsolutions/">Cool Solutions</a>, including: </p> Index: dependencychecks.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/dependencychecks.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** dependencychecks.html 30 Aug 2007 06:37:53 -0000 1.4 --- dependencychecks.html 30 Aug 2007 22:35:05 -0000 1.5 *************** *** 1,2 **** --- 1,4 ---- + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> + <html> <head> *************** *** 14,23 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Predictive Dependency Checks</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 55,59 **** <p> ! <img src="images/predictive-dependency-checks.png" border="0"> </p> --- 55,59 ---- <p> ! <img src="images/predictive-dependency-checks.png" border="0" alt="Predictive Dependency Checks" title="Predictive Dependency Checks"> </p> Index: servicechecks.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/servicechecks.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** servicechecks.html 30 Aug 2007 06:38:15 -0000 1.4 --- servicechecks.html 30 Aug 2007 22:35:09 -0000 1.5 *************** *** 1,2 **** --- 1,4 ---- + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> + <html> <head> *************** *** 14,23 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Service Checks</h1> </div> - </p> <hr> --- 16,23 ---- Index: tuning.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/tuning.html,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** tuning.html 30 Aug 2007 06:38:16 -0000 1.9 --- tuning.html 30 Aug 2007 22:35:09 -0000 1.10 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Tuning Nagios For Maximum Performance</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 34,38 **** </p> ! <img src="images/tuning.png" border="0" style="float: right; clear: both;"> <p> --- 32,36 ---- </p> ! <img src="images/tuning.png" border="0" style="float: right; clear: both;" alt="Tuning" title="Tuning"> <p> *************** *** 48,83 **** <ol> ! <li><b>Graph performance statistics with MRTG</b>. In order to keep track of how well your Nagios installation handles load over time and how your configuration changes affect it, you should be graphing several important statistics with MRTG. This is really, really, really useful when it comes to tuning the performance of a Nagios installation. Really. Information on how to do this can be found <a href="mrtggraphs.html">here</a>.</li><br><br> ! <li><b>Use large installation tweaks</b>. Enabling the <a href="configmain.html#use_large_installation_tweaks">use_large_installation_tweaks</a> option may provide you with better performance. Read more about what this option does <a href="largeinstalltweaks.html">here</a>.<br><br> ! <li><b>Check Result Reaper Frequency</b>. The <a href="configmain.html#check_result_reaper_frequency">check_result_reaper_frequency</a> variable determines how often Nagios should check for host and service check results that need to be processed. The maximum amount of time it can spend processing those results is determined by the max reaper time (see below). If your reaper frequency is too high (too infrequent), you might see high latencies for host and service checks.<br><br> ! <li><b>Max Reaper Time</b>. The <a href="configmain.html#max_check_result_reaper_time">max_check_result_reaper_time</a> variables determines the maximum amount of time the Nagios daemon can spend processing the results of host and service checks before moving on to other things - like executing new host and service checks. Too high of a value can result in large latencies for your host and service checks. Too low of a value can have the same effect. If you're experiencing high latencies, adjust this variable and see what effect it has. Again, you should be <a href="mrtggraphs.html">graphing statistics</a> in order to make this determination.<br><br> ! <li><b>Adjust buffer slots</b>. You may need to adjust the values of the <a href="configmain.html#check_result_buffer_slots">check_result_buffer_slots</a> and <a href="configmain.html#external_command_buffer_slots">external_command_buffer_slots</a> options. Graphing buffer slot statistics with <a href="mrtggraphs.html">MRTG</a> (see above) is critical in determining what values you should use for these options.</li><br><br> ! <li><b>Check service latencies to determine best value for maximum concurrent checks</b>. Nagios can restrict the number of maximum concurrently executing service checks to the value you specify with the <a href="configmain.html#max_concurrent_checks">max_concurrent_checks</a> option. This is good because it gives you some control over how much load Nagios will impose on your monitoring host, but it can also slow things down. If you are seeing high latency values (> 10 or 15 seconds) for the majority of your service checks (via the <a href="cgis.html#extinfo_cgi">extinfo CGI</a>), you are probably starving Nagios of the checks it needs. That's not Nagios's fault - its yours. Under ideal conditions, all service checks would have a latency of 0, meaning they were executed at the exact time that they were scheduled to be executed. However, it is normal for some checks to have small latency values. I would recommend taking the minimum number of maximum concurrent checks reported when running Nagios with the <b>-s</b> command line argument and doubling it. Keep increasing it until the average check latency for your services is fairly low. More information on service check scheduling can be found <a href="checkscheduling.html">here</a>.<br><br> ! <li><b>Use passive checks when possible</b>. The overhead needed to process the results of <a href="passivechecks.html">passive service checks</a> is much lower than that of "normal" active checks, so make use of that piece of info if you're monitoring a slew of services. It should be noted that passive service checks are only really useful if you have some external application doing some type of monitoring or reporting, so if you're having Nagios do all the work, this won't help things.<br><br> ! <li><b>Avoid using interpreted plugins</b>. One thing that will significantly reduce the load on your monitoring host is the use of compiled (C/C++, etc.) plugins rather than interpreted script (Perl, etc) plugins. While Perl scripts and such are easy to write and work well, the fact that they are compiled/interpreted at every execution instance can significantly increase the load on your monitoring host if you have a lot of service checks. If you want to use Perl plugins, consider compiling them into true executables using perlcc(1) (a utility which is part of the standard Perl distribution) or compiling Nagios with an embedded Perl interpreter (see below).<br><br> ! <li><b>Use the embedded Perl interpreter</b>. If you're using a lot of Perl scripts for service checks, etc., you will probably find that compiling the <a href="embeddedperl.html">embedded Perl interpreter</a> into the Nagios binary will speed things up. ! <br><br> ! <li><b>Optimize host check commands</b>. If you're checking host states using the check_ping plugin you'll find that host checks will be performed much faster if you break up the checks. Instead of specifying a <i>max_attempts</i> value of 1 in the host definition and having the check_ping plugin send 10 ICMP packets to the host, it would be much faster to set the <i>max_attempts</i> value to 10 and only send out 1 ICMP packet each time. This is due to the fact that Nagios can often determine the status of a host after executing the plugin once, so you want to make the first check as fast as possible. This method does have its pitfalls in some situations (i.e. hosts that are slow to respond may be assumed to be down), but I you'll see faster host checks if you use it. Another option would be to use a faster plugin (i.e. check_fping) as the <i>host_check_command</i> instead of check_ping.<br><br> ! <li><b>Schedule regular host checks</b>. Scheduling regular checks of hosts can actually help performance in Nagios. This is due to the way the <a href="cachedchecks.html">cached check logic</a> works (see below). Prior to Nagios 3, regularly scheduled host checks used to result in a big performance hit. This is no longer the case, as host checks are run in parallel - just like service checks. To schedule regular checks of a host, set the <i>check_interval</i> directive in the <a href="objectdefinitions.html#host">host definition</a> to something greater than 0.<br><br> ! <li><b>Enable cached host checks</b>. Beginning in Nagios 3, on-demand host checks can benefit from caching. On-demand host checks are performed whenever Nagios detects a service state change. These on-demand checks are executed because Nagios wants to know if the host associated with the service changed state. By enabling cached host checks, you can optimize performance. In some cases, Nagios may be able to used the old/cached state of the host, rather than actually executing a host check command. This can speed things up and reduce load on monitoring server. In order for cached checks to be effective, you need to schedule regular checks of your hosts (see above). More information on cached checks can be found <a href="cachedchecks.html">here</a>.<br><br> ! <li><b>Don't use agressive host checking</b>. Unless you're having problems with Nagios recognizing host recoveries, I would recommend not enabling the <a href="configmain.html#use_agressive_host_checking">use_aggressive_host_checking</a> option. With this option turned off host checks will execute much faster, resulting in speedier processing of service check results. However, host recoveries can be missed under certain circumstances when this it turned off. For example, if a host recovers and all of the services associated with that host stay in non-OK states (and don't "wobble" between different non-OK states), Nagios may miss the fact that the host has recovered. A few people may need to enable this option, but the majority don't and I would recommendnot using it unless you find it necessary... ! <br><br> ! <li><b>External command optimizations</b>. If you're processing a lot of external commands (i.e. passive checks in a <a href="distributed.html">distributed setup</a>, you'll probably want to set the <a href="configmain.html#command_check_interval">command_check_interval</a> variable to <b>-1</b>. This will cause Nagios to check for external commands as often as possible. You should also consider increasing the number of available <a href="configmain.html#external_command_buffer_slots">external command buffer slots</a>. Buffers slots are used to hold external commands that have been read from the <a href="configmain.html#command_file">external command file</a> (by a separate thread) before they are processed by the Nagios daemon. If your Nagios daemon is receiving a lot of passive checks or external commands, you could end up in a situation where the buffers are always full. This results in child processes (external scripts, NSCA daemon, etc.) blocking when they attempt to write to the external command file. I would highly recommend that you graph external command buffer slot usage using MRTG and the nagiostats utility as described <a href="mrtggraphs.html">here</a>, so you understand the typical external command buffer usage of your Nagios installation. ! <br><br> ! <li><b>Optimize hardware for maximum performance</b>. NOTE: Hardware performance shouldn't be an issue unless: 1) you're monitoring thousands of services, 2) you're doing a lot of post-processing of performance data, etc. Your system configuration and your hardware setup are going to directly affect how your operating system performs, so they'll affect how Nagios performs. The most common hardware optimization you can make is with your hard drives. CPU and memory speed are obviously factors that affect performance, but disk access is going to be your biggest bottlenck. Don't store plugins, the status log, etc on slow drives (i.e. old IDE drives or NFS mounts). If you've got them, use UltraSCSI drives or fast IDE drives. An important note for IDE/Linux users is that many Linux installations do not attempt to optimize disk access. If you don't change the disk access parameters (by using a utility like <b>hdparam</b>), you'll loose out on a <b>lot</b> of the speedy features of the new IDE drives. </ol> --- 46,78 ---- <ol> ! <li><b>Graph performance statistics with MRTG</b>. In order to keep track of how well your Nagios installation handles load over time and how your configuration changes affect it, you should be graphing several important statistics with MRTG. This is really, really, really useful when it comes to tuning the performance of a Nagios installation. Really. Information on how to do this can be found <a href="mrtggraphs.html">here</a>.<br><br></li> ! <li><b>Use large installation tweaks</b>. Enabling the <a href="configmain.html#use_large_installation_tweaks">use_large_installation_tweaks</a> option may provide you with better performance. Read more about what this option does <a href="largeinstalltweaks.html">here</a>.<br><br></li> ! <li><b>Check Result Reaper Frequency</b>. The <a href="configmain.html#check_result_reaper_frequency">check_result_reaper_frequency</a> variable determines how often Nagios should check for host and service check results that need to be processed. The maximum amount of time it can spend processing those results is determined by the max reaper time (see below). If your reaper frequency is too high (too infrequent), you might see high latencies for host and service checks.<br><br></li> ! <li><b>Max Reaper Time</b>. The <a href="configmain.html#max_check_result_reaper_time">max_check_result_reaper_time</a> variables determines the maximum amount of time the Nagios daemon can spend processing the results of host and service checks before moving on to other things - like executing new host and service checks. Too high of a value can result in large latencies for your host and service checks. Too low of a value can have the same effect. If you're experiencing high latencies, adjust this variable and see what effect it has. Again, you should be <a href="mrtggraphs.html">graphing statistics</a> in order to make this determination.<br><br></li> ! <li><b>Adjust buffer slots</b>. You may need to adjust the value of the <a href="configmain.html#external_command_buffer_slots">external_command_buffer_slots</a> option. Graphing buffer slot statistics with <a href="mrtggraphs.html">MRTG</a> (see above) is critical in determining what values you should use for this option.<br><br></li> ! <li><b>Check service latencies to determine best value for maximum concurrent checks</b>. Nagios can restrict the number of maximum concurrently executing service checks to the value you specify with the <a href="configmain.html#max_concurrent_checks">max_concurrent_checks</a> option. This is good because it gives you some control over how much load Nagios will impose on your monitoring host, but it can also slow things down. If you are seeing high latency values (> 10 or 15 seconds) for the majority of your service checks (via the <a href="cgis.html#extinfo_cgi">extinfo CGI</a>), you are probably starving Nagios of the checks it needs. That's not Nagios's fault - its yours. Under ideal conditions, all service checks would have a latency of 0, meaning they were executed at the exact time that they were scheduled to be executed. However, it is normal for some checks to have small latency values. I would recommend taking the minimum number of maximum concurrent checks reported when running Nagios with the <b>-s</b> command line argument and doubling it. Keep increasing it until the average check latency for your services is fairly low. More information on service check scheduling can be found <a href="checkscheduling.html">here</a>.<br><br></li> ! <li><b>Use passive checks when possible</b>. The overhead needed to process the results of <a href="passivechecks.html">passive service checks</a> is much lower than that of "normal" active checks, so make use of that piece of info if you're monitoring a slew of services. It should be noted that passive service checks are only really useful if you have some external application doing some type of monitoring or reporting, so if you're having Nagios do all the work, this won't help things.<br><br></li> ! <li><b>Avoid using interpreted plugins</b>. One thing that will significantly reduce the load on your monitoring host is the use of compiled (C/C++, etc.) plugins rather than interpreted script (Perl, etc) plugins. While Perl scripts and such are easy to write and work well, the fact that they are compiled/interpreted at every execution instance can significantly increase the load on your monitoring host if you have a lot of service checks. If you want to use Perl plugins, consider compiling them into true executables using perlcc(1) (a utility which is part of the standard Perl distribution) or compiling Nagios with an embedded Perl interpreter (see below).<br><br></li> ! <li><b>Use the embedded Perl interpreter</b>. If you're using a lot of Perl scripts for service checks, etc., you will probably find that compiling the <a href="embeddedperl.html">embedded Perl interpreter</a> into the Nagios binary will speed things up.<br><br></li> ! <li><b>Optimize host check commands</b>. If you're checking host states using the check_ping plugin you'll find that host checks will be performed much faster if you break up the checks. Instead of specifying a <i>max_attempts</i> value of 1 in the host definition and having the check_ping plugin send 10 ICMP packets to the host, it would be much faster to set the <i>max_attempts</i> value to 10 and only send out 1 ICMP packet each time. This is due to the fact that Nagios can often determine the status of a host after executing the plugin once, so you want to make the first check as fast as possible. This method does have its pitfalls in some situations (i.e. hosts that are slow to respond may be assumed to be down), but I you'll see faster host checks if you use it. Another option would be to use a faster plugin (i.e. check_fping) as the <i>host_check_command</i> instead of check_ping.<br><br></li> ! <li><b>Schedule regular host checks</b>. Scheduling regular checks of hosts can actually help performance in Nagios. This is due to the way the <a href="cachedchecks.html">cached check logic</a> works (see below). Prior to Nagios 3, regularly scheduled host checks used to result in a big performance hit. This is no longer the case, as host checks are run in parallel - just like service checks. To schedule regular checks of a host, set the <i>check_interval</i> directive in the <a href="objectdefinitions.html#host">host definition</a> to something greater than 0.<br><br></li> ! <li><b>Enable cached host checks</b>. Beginning in Nagios 3, on-demand host checks can benefit from caching. On-demand host checks are performed whenever Nagios detects a service state change. These on-demand checks are executed because Nagios wants to know if the host associated with the service changed state. By enabling cached host checks, you can optimize performance. In some cases, Nagios may be able to used the old/cached state of the host, rather than actually executing a host check command. This can speed things up and reduce load on monitoring server. In order for cached checks to be effective, you need to schedule regular checks of your hosts (see above). More information on cached checks can be found <a href="cachedchecks.html">here</a>.<br><br></li> ! <li><b>Don't use agressive host checking</b>. Unless you're having problems with Nagios recognizing host recoveries, I would recommend not enabling the <a href="configmain.html#use_agressive_host_checking">use_aggressive_host_checking</a> option. With this option turned off host checks will execute much faster, resulting in speedier processing of service check results. However, host recoveries can be missed under certain circumstances when this it turned off. For example, if a host recovers and all of the services associated with that host stay in non-OK states (and don't "wobble" between different non-OK states), Nagios may miss the fact that the host has recovered. A few people may need to enable this option, but the majority don't and I would recommendnot using it unless you find it necessary...<br><br></li> ! <li><b>External command optimizations</b>. If you're processing a lot of external commands (i.e. passive checks in a <a href="distributed.html">distributed setup</a>, you'll probably want to set the <a href="configmain.html#command_check_interval">command_check_interval</a> variable to <b>-1</b>. This will cause Nagios to check for external commands as often as possible. You should also consider increasing the number of available <a href="configmain.html#external_command_buffer_slots">external command buffer slots</a>. Buffers slots are used to hold external commands that have been read from the <a href="configmain.html#command_file">external command file</a> (by a separate thread) before they are processed by the Nagios daemon. If your Nagios daemon is receiving a lot of passive checks or external commands, you could end up in a situation where the buffers are always full. This results in child processes (external scripts, NSCA daemon, etc.) blocking when they attempt to write to the external command file. I would highly recommend that you graph external command buffer slot usage using MRTG and the nagiostats utility as described <a href="mrtggraphs.html">here</a>, so you understand the typical external command buffer usage of your Nagios installation.<br><br></li> ! <li><b>Optimize hardware for maximum performance</b>. NOTE: Hardware performance shouldn't be an issue unless: 1) you're monitoring thousands of services, 2) you're doing a lot of post-processing of performance data, etc. Your system configuration and your hardware setup are going to directly affect how your operating system performs, so they'll affect how Nagios performs. The most common hardware optimization you can make is with your hard drives. CPU and memory speed are obviously factors that affect performance, but disk access is going to be your biggest bottlenck. Don't store plugins, the status log, etc on slow drives (i.e. old IDE drives or NFS mounts). If you've got them, use UltraSCSI drives or fast IDE drives. An important note for IDE/Linux users is that many Linux installations do not attempt to optimize disk access. If you don't change the disk access parameters (by using a utility like <b>hdparam</b>), you'll loose out on a <b>lot</b> of the speedy features of the new IDE drives.<br><br></li> </ol> Index: addons.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/addons.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** addons.html 30 Aug 2007 06:37:51 -0000 1.7 --- addons.html 30 Aug 2007 22:35:03 -0000 1.8 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Nagios Addons</h1> </div> - </p> <hr> --- 16,23 ---- Index: escalations.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/escalations.html,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** escalations.html 30 Aug 2007 06:37:54 -0000 1.8 --- escalations.html 30 Aug 2007 22:35:06 -0000 1.9 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Notification Escalations</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 34,38 **** </p> ! <img src="images/objects-contacts.png" border="0" style="float: right;"> <p> --- 32,36 ---- </p> ! <img src="images/objects-contacts.png" border="0" style="float: right;" alt="Contacts" title="Contacts"> <p> *************** *** 71,75 **** } </pre> - </p> <p> --- 69,72 ---- *************** *** 104,108 **** } </pre> - </p> <p> --- 101,104 ---- *************** *** 137,141 **** } </pre> - </p> <p> --- 133,136 ---- *************** *** 176,180 **** } </pre> - </p> <p> --- 171,174 ---- *************** *** 209,213 **** } </pre> - </p> <p> --- 203,206 ---- *************** *** 238,242 **** } </pre> - </p> <p> --- 231,234 ---- *************** *** 276,280 **** } </pre> - </p> <p> --- 268,271 ---- Index: nagiostats.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/nagiostats.html,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** nagiostats.html 30 Aug 2007 06:38:03 -0000 1.5 --- nagiostats.html 30 Aug 2007 22:35:08 -0000 1.6 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Using The Nagiostats Utility</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 54,59 **** </p> ! <p> ! <dir> <pre> [nagios@lanman ~]# /usr/local/nagios/bin/nagiostats -c /usr/local/nagios/etc/nagios.cfg --- 52,56 ---- </p> ! <pre> [nagios@lanman ~]# /usr/local/nagios/bin/nagiostats -c /usr/local/nagios/etc/nagios.cfg *************** *** 123,128 **** [nagios@lanman ~]# </pre> - </dir> - </p> <p> --- 120,123 ---- Index: networkreachability.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/networkreachability.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** networkreachability.html 30 Aug 2007 06:38:04 -0000 1.7 --- networkreachability.html 30 Aug 2007 22:35:08 -0000 1.8 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Determining Status and Reachability of Network Hosts</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 56,60 **** <p> ! <img src="images/reachability1.png" border="0"> </p> --- 54,58 ---- <p> ! <img src="images/reachability1.png" border="0" alt="Example Network" title="Example Network"> </p> *************** *** 68,72 **** <p> ! <img src="images/reachability2.png" border="0"> </p> --- 66,70 ---- <p> ! <img src="images/reachability2.png" border="0" alt="Parent/Child Relationships" title="Parent/Child Relationships"> </p> *************** *** 136,140 **** <p> ! <img src="images/reachability3.png" border="0"> </p> --- 134,138 ---- <p> ! <img src="images/reachability3.png" border="0" alt="Reachability Example" title="Reachability Example"> </p> *************** *** 144,148 **** <p> ! <img src="images/reachability4.png" border="0"> </p> --- 142,146 ---- <p> ! <img src="images/reachability4.png" border="0" alt="Reachability Logic" title="Reachability Logic"> </p> Index: int-snmptrap.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/int-snmptrap.html,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** int-snmptrap.html 30 Aug 2007 06:37:59 -0000 1.8 --- int-snmptrap.html 30 Aug 2007 22:35:06 -0000 1.9 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">SNMP Trap Integration</h1> </div> - </p> <hr> --- 16,23 ---- Index: configobject.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/configobject.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** configobject.html 30 Aug 2007 06:37:52 -0000 1.7 --- configobject.html 30 Aug 2007 22:35:05 -0000 1.8 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Object Configuration Overview</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 71,75 **** </p> ! </p> Objects are defined in a flexible template format, which can make it much easier to manage your Nagios configuration in the long term. Basic information on how to define objects in your configuration files can be found <a href="objectdefinitions.html">here</a>. </p> --- 69,73 ---- </p> ! <p> Objects are defined in a flexible template format, which can make it much easier to manage your Nagios configuration in the long term. Basic information on how to define objects in your configuration files can be found <a href="objectdefinitions.html">here</a>. </p> Index: configcgi.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/configcgi.html,v retrieving revision 1.17 retrieving revision 1.18 diff -C2 -d -r1.17 -r1.18 *** configcgi.html 30 Aug 2007 06:37:52 -0000 1.17 --- configcgi.html 30 Aug 2007 22:35:04 -0000 1.18 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">CGI Configuration File Options</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 57,60 **** --- 55,67 ---- <p> + <strong><u>Configuration File Variables</u></strong> + </p> + + <p> + Below you will find descriptions of each main Nagios configuration file option... + </p> + + <!-- + <p> <strong><u>Index</u></strong> </p> *************** *** 94,99 **** <a href="#splunk_url">Splunk URL</a><br> </p> - <p> <a name="main_cfg_file"></a> <table border="0" width="100%" class="Default"> --- 101,106 ---- <a href="#splunk_url">Splunk URL</a><br> </p> + //--> <a name="main_cfg_file"></a> <table border="0" width="100%" class="Default"> *************** *** 102,108 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 109,114 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 115,119 **** </tr> </table> - </p> <p> --- 121,124 ---- *************** *** 121,125 **** </p> - <p> <a name="physical_html_path"></a> <table border="0" width="100%" class="Default"> --- 126,129 ---- *************** *** 128,134 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 132,137 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 141,145 **** </tr> </table> - </p> <p> --- 144,147 ---- *************** *** 149,153 **** - <p> <a name="url_html_path"></a> <table border="0" width="100%" class="Default"> --- 151,154 ---- *************** *** 156,162 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 157,162 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 169,173 **** </tr> </table> - </p> <p> --- 169,172 ---- *************** *** 177,181 **** - <p> <a name="use_authentication"></a> <table border="0" width="100%" class="Default"> --- 176,179 ---- *************** *** 184,190 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 182,187 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 197,204 **** </tr> </table> - </p> <p> ! This option controls whether or not the CGIs will use the authentication and authorization functionality when determining what information and commands users have access to. I would strongly suggest that you use the authentication functionality for the CGIs. If you decide not to use authentication, make sure to remove the <a href="cgis.html#command_cgi">command CGI</a> to prevent unauthorized users from issuing commands to Nagios. The CGI will not issue commands to Nagios if authentication is disabled, but I would suggest removing it altogether just to be on the safe side. More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>. </p> <ul> --- 194,200 ---- </tr> </table> <p> ! This option controls whether or not the CGIs will use the authentication and authorization functionality when determining what information and commands users have access to. I would strongly suggest that you use the authentication functionality for the CGIs. If you decide not to use authentication, make sure to remove the <a href="cgis.html#cmd_cgi">command CGI</a> to prevent unauthorized users from issuing commands to Nagios. The CGI will not issue commands to Nagios if authentication is disabled, but I would suggest removing it altogether just to be on the safe side. More information on how to setup authentication and configure authorization for the CGIs can be found <a href="cgiauth.html">here</a>. </p> <ul> *************** *** 208,212 **** - <p> <a name="default_user_name"></a> <table border="0" width="100%" class="Default"> --- 204,207 ---- *************** *** 215,221 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 210,215 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 228,232 **** </tr> </table> - </p> <p> --- 222,225 ---- *************** *** 237,241 **** </p> - <p> <a name="authorized_for_system_information"></a> <table border="0" width="100%" class="Default"> --- 230,233 ---- *************** *** 244,250 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 236,241 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 257,261 **** </tr> </table> - </p> <p> --- 248,251 ---- *************** *** 264,268 **** - <p> <a name="authorized_for_system_commands"></a> <table border="0" width="100%" class="Default"> --- 254,257 ---- *************** *** 271,277 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 260,265 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 284,288 **** </tr> </table> - </p> <p> --- 272,275 ---- *************** *** 291,295 **** - <p> <a name="authorized_for_configuration_information"></a> <table border="0" width="100%" class="Default"> --- 278,281 ---- *************** *** 298,304 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 284,289 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 311,315 **** </tr> </table> - </p> <p> --- 296,299 ---- *************** *** 318,322 **** - <p> <a name="authorized_for_all_hosts"></a> <table border="0" width="100%" class="Default"> --- 302,305 ---- *************** *** 325,331 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 308,313 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 338,342 **** </tr> </table> - </p> <p> --- 320,323 ---- *************** *** 345,349 **** - <p> <a name="authorized_for_all_host_commands"></a> <table border="0" width="100%" class="Default"> --- 326,329 ---- *************** *** 352,358 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 332,337 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 365,369 **** </tr> </table> - </p> <p> --- 344,347 ---- *************** *** 372,376 **** - <p> <a name="authorized_for_all_services"></a> <table border="0" width="100%" class="Default"> --- 350,353 ---- *************** *** 379,385 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 356,361 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 392,396 **** </tr> </table> - </p> <p> --- 368,371 ---- *************** *** 399,403 **** - <p> <a name="authorized_for_all_service_commands"></a> <table border="0" width="100%" class="Default"> --- 374,377 ---- *************** *** 406,412 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 380,385 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 419,423 **** </tr> </table> - </p> <p> --- 392,395 ---- *************** *** 427,431 **** - <p> <a name="lock_author_names"></a> <table border="0" width="100%" class="Default"> --- 399,402 ---- *************** *** 434,440 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 405,410 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 447,451 **** </tr> </table> - </p> <p> --- 417,420 ---- *************** *** 458,462 **** - <p> <a name="statusmap_background_image"></a> <table border="0" width="100%" class="Default"> --- 427,430 ---- *************** *** 465,471 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 433,438 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 478,482 **** </tr> </table> - </p> <p> --- 445,448 ---- *************** *** 485,489 **** - <p> <a name="default_statusmap_layout"></a> <table border="0" width="100%" class="Default"> --- 451,454 ---- *************** *** 492,498 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 457,462 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 505,509 **** </tr> </table> - </p> <p> --- 469,472 ---- *************** *** 511,515 **** </p> - <p> <table border=1 cellspacing=0 cellpadding=5 class="Default"> <tr><th><layout_number> Value</th><th>Layout Method</th></tr> --- 474,477 ---- *************** *** 522,529 **** <tr><td>6</td><td>Circular (Balloon)</td></tr> </table> - </p> - <p> <a name="statuswrl_include"></a> <table border="0" width="100%" class="Default"> --- 484,489 ---- *************** *** 532,538 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 492,497 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 545,549 **** </tr> </table> - </p> <p> --- 504,507 ---- *************** *** 553,557 **** - <p> <a name="default_statuswrl_layout"></a> <table border="0" width="100%" class="Default"> --- 511,514 ---- *************** *** 560,566 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 517,522 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 573,577 **** </tr> </table> - </p> <p> --- 529,532 ---- *************** *** 579,583 **** </p> - <p> <table border=1 cellspacing=0 cellpadding=5 class="Default"> <tr><th><layout_number> Value</th><th>Layout Method</th></tr> --- 534,537 ---- *************** *** 587,594 **** <tr><td>4</td><td>Circular</td></tr> </table> - </p> - <p> <a name="refresh_rate"></a> <table border="0" width="100%" class="Default"> --- 541,546 ---- *************** *** 597,603 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 549,554 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 610,614 **** </tr> </table> - </p> <p> --- 561,564 ---- *************** *** 617,621 **** - <p> <a name="audio_alerts"></a> <table border="0" width="100%" class="Default"> --- 567,570 ---- *************** *** 624,630 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 573,578 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 649,653 **** </tr> </table> - </p> <p> --- 597,600 ---- *************** *** 655,659 **** </p> - <p> <a name="ping_syntax"></a> <table border="0" width="100%" class="Default"> --- 602,605 ---- *************** *** 662,668 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 608,613 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 675,679 **** </tr> </table> - </p> <p> --- 620,623 ---- *************** *** 683,687 **** - <p> <a name="escape_html_tags"></a> <table border="0" width="100%" class="Default"> --- 627,630 ---- *************** *** 690,696 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 633,638 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 703,707 **** </tr> </table> - </p> <p> --- 645,648 ---- *************** *** 710,714 **** - <p> <a name="notes_url_target"></a> <table border="0" width="100%" class="Default"> --- 651,654 ---- *************** *** 717,723 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 657,662 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 730,734 **** </tr> </table> - </p> <p> --- 669,672 ---- *************** *** 737,741 **** - <p> <a name="action_url_target"></a> <table border="0" width="100%" class="Default"> --- 675,678 ---- *************** *** 744,750 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 681,686 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 757,761 **** </tr> </table> - </p> <p> --- 693,696 ---- *************** *** 764,768 **** - <p> <a name="enable_splunk_integration"></a> <table border="0" width="100%" class="Default"> --- 699,702 ---- *************** *** 771,777 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 705,710 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 784,788 **** </tr> </table> - </p> <p> --- 717,720 ---- *************** *** 790,794 **** </p> - <p> <a name="splunk_url"></a> <table border="0" width="100%" class="Default"> --- 722,725 ---- *************** *** 797,803 **** </tr> </table> ! </p> - <p> <table border="0" class="Default"> <tr> --- 728,733 ---- </tr> </table> ! <br> <table border="0" class="Default"> <tr> *************** *** 810,814 **** </tr> </table> - </p> <p> --- 740,743 ---- Index: redundancy.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/redundancy.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** redundancy.html 30 Aug 2007 06:38:13 -0000 1.7 --- redundancy.html 30 Aug 2007 22:35:09 -0000 1.8 *************** *** 1,2 **** --- 1,4 ---- + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> + <html> <head> *************** *** 14,22 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <h1 class="PageTitle">Redundant and Failover Network Monitoring</h1> </div> - </p> <hr> --- 16,22 ---- *************** *** 61,65 **** <li>Issuing <a href="extcommands.html">external commands</a> to Nagios via shell scripts <li>Executing plugins on remote hosts using either the <a href="addons.html#nrpe">NRPE addon</a> or some other method ! <li>Checking the status of the Nagios process with the <a href="plugins.html#check_nagios">check_nagios</a> plugin </ul> --- 61,65 ---- <li>Issuing <a href="extcommands.html">external commands</a> to Nagios via shell scripts <li>Executing plugins on remote hosts using either the <a href="addons.html#nrpe">NRPE addon</a> or some other method ! <li>Checking the status of the Nagios process with the <i>check_nagios</i> plugin </ul> Index: clusters.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/clusters.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** clusters.html 30 Aug 2007 06:37:52 -0000 1.7 --- clusters.html 30 Aug 2007 22:35:04 -0000 1.8 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Monitoring Service and Host Clusters</h1> </div> - </p> <hr> --- 16,23 ---- Index: activechecks.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/activechecks.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** activechecks.html 30 Aug 2007 06:37:50 -0000 1.4 --- activechecks.html 30 Aug 2007 22:35:03 -0000 1.5 *************** *** 1,2 **** --- 1,4 ---- + <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> + <html> <head> *************** *** 14,23 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Active Checks</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 41,45 **** </ul> ! <img src="images/activechecks.png" border="0" style="float: right;"> <p> --- 41,45 ---- </ul> ! <img src="images/activechecks.png" border="0" style="float: right;" alt="Active Checks"> <p> Index: oncallrotation.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/oncallrotation.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** oncallrotation.html 30 Aug 2007 06:38:06 -0000 1.4 --- oncallrotation.html 30 Aug 2007 22:35:08 -0000 1.5 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">On-Call Rotations</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 34,40 **** </p> ! <img src="images/objects-contacts.png" border="0" style="float: right;"> ! <img src="images/objects-timeperiods.png" border="0" style="float: right;"> <p> --- 32,38 ---- </p> ! <img src="images/objects-contacts.png" border="0" style="float: right; margin: 0 0 0 10px;" alt="Contacts" title="Contacts"> ! <img src="images/objects-timeperiods.png" border="0" style="float: right;" alt="Timeperiods" title="Timeperiods"> <p> Index: verifyconfig.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/verifyconfig.html,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** verifyconfig.html 30 Aug 2007 06:38:19 -0000 1.6 --- verifyconfig.html 30 Aug 2007 22:35:09 -0000 1.7 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Verifying Your Configuration</h1> </div> - </p> <hr> --- 16,23 ---- Index: dependencies.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/dependencies.html,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -d -r1.11 -r1.12 *** dependencies.html 30 Aug 2007 06:37:53 -0000 1.11 --- dependencies.html 30 Aug 2007 22:35:05 -0000 1.12 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Host and Service Dependencies</h1> </div> - </p> <hr> --- 16,23 ---- Index: monitoring-routers.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/monitoring-routers.html,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** monitoring-routers.html 30 Aug 2007 06:38:02 -0000 1.6 --- monitoring-routers.html 30 Aug 2007 22:35:08 -0000 1.7 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Monitoring Routers and Switches</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 34,38 **** </p> ! <img src="images/switch.png" border="0" style="float: right"> <p> --- 32,36 ---- </p> ! <img src="images/switch.png" border="0" style="float: right" alt="Switch"> <p> Index: monitoring-printers.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/monitoring-printers.html,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** monitoring-printers.html 30 Aug 2007 06:38:02 -0000 1.8 --- monitoring-printers.html 30 Aug 2007 22:35:07 -0000 1.9 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Monitoring Network Printers</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 34,38 **** </p> ! <img src="images/printer.png" border="0" style="float: right"> <p> --- 32,36 ---- </p> ! <img src="images/printer.png" border="0" style="float: right" alt="Printer"> <p> Index: index.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/index.html,v retrieving revision 1.21 retrieving revision 1.22 diff -C2 -d -r1.21 -r1.22 *** index.html 18 Jun 2007 16:56:28 -0000 1.21 --- index.html 30 Aug 2007 22:35:06 -0000 1.22 *************** *** 28,36 **** <body bgcolor="#FFFFFF" text="black" CLASS="Default"> - <P> <div align="center"> <img src="images/logofullsize.png" border=0 alt="Nagios"> </div> - </P> <h1 class="PageTitle"> --- 28,34 ---- Index: passivechecks.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/passivechecks.html,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** passivechecks.html 30 Aug 2007 06:38:07 -0000 1.9 --- passivechecks.html 30 Aug 2007 22:35:09 -0000 1.10 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <div align="center"> <img src="images/nagios.jpg" border="0" alt="Nagios" title="Nagios"> <h1 class="PageTitle">Passive Checks</h1> </div> - </p> <hr> --- 16,23 ---- *************** *** 72,76 **** </p> ! <img src="images/passivechecks.png" border="0" style="float: right; padding: 0 0 10px 10px;"> <p> --- 70,74 ---- </p> ! <img src="images/passivechecks.png" border="0" style="float: right; padding: 0 0 10px 10px;" alt="Passive Checks" title="Passive Checks"> <p> *************** *** 79,86 **** <ol> ! <li>An external application checks the status of a host or service.</li><br><br> ! <li>The external application writes the results of the check to the <a href="configmain.html#command_file">external command file</a>.</li><br><br> ! <li>The next time Nagios reads the external command file it will place the results of all passive checks into a queue for later processing. The same queue that is used for storing results from active checks is also used to store the results from passive checks.</li><br><br> ! <li>Nagios will periodically execute a <a href="configmain.html#check_result_reaper_frequency">check result reaper event</a> and scan the check result queue. Each service check result that is found in the queue is processed in the same manner - regardless of whether the check was active or passive. Nagios may send out notifications, log alerts, etc. depending on the check result information.</li><br><br> </ol> --- 77,84 ---- <ol> ! <li>An external application checks the status of a host or service.<br><br></li> ! <li>The external application writes the results of the check to the <a href="configmain.html#command_file">external command file</a>.<br><br></li> ! <li>The next time Nagios reads the external command file it will place the results of all passive checks into a queue for later processing. The same queue that is used for storing results from active checks is also used to store the results from passive checks.<br><br></li> ! <li>Nagios will periodically execute a <a href="configmain.html#check_result_reaper_frequency">check result reaper event</a> and scan the check result queue. Each service check result that is found in the queue is processed in the same manner - regardless of whether the check was active or passive. Nagios may send out notifications, log alerts, etc. depending on the check result information.<br><br></li> </ol> *************** *** 204,208 **** </p> ! <img src="images/nsca.png" border="0" style="float: right; padding: 0 0 10px 10px;"> <p> --- 202,206 ---- </p> ! <img src="images/nsca.png" border="0" style="float: right; padding: 0 0 10px 10px;" alt="NSCA Addon" title="NSCA Addon"> <p> Index: largeinstalltweaks.html =================================================================== RCS file: /cvsroot/nagios/nagios/html/docs/largeinstalltweaks.html,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** largeinstalltweaks.html 30 Aug 2007 06:38:00 -0000 1.3 --- largeinstalltweaks.html 30 Aug 2007 22:35:07 -0000 1.4 *************** *** 16,25 **** <body bgcolor="#FFFFFF" text="black" class="Default"> - <p> <... [truncated message content] |
Thanks for helping keep SourceForge clean.
X