projected/recommended service check option

[jeff vier]

On Thu, 2004-01-29 at 15:13, Neil wrote:
> I also took out lines that are just paths. Here it is. 
<snip>
Looks pretty much like mine.
here's the differences (in a kind of mangled diff -u format):
--- you
+++ me
-log_event_handlers=1
+log_event_handlers=0
-log_initial_states=0
+log_initial_states=1
-max_concurrent_checks=15
+max_concurrent_checks=150
-service_reaper_frequency=10
+service_reaper_frequency=15s
-retention_update_interval=60
+retention_update_interval=14
-use_retained_program_state=0
+use_retained_program_state=1
-process_performance_data=0
+process_performance_data=1
-check_for_orphaned_services=0
+check_for_orphaned_services=1
-freshness_check_interval=60
+freshness_check_interval=300
-aggregate_status_updates=1
+aggregate_status_updates=0


> Actually, below is how it looks now. I found out after tweaking 
> service_reaper_frequency and interval_lenght. I even got it to a recommended 
> value of 186. :) But I don't know if it's good for a production monitoring 
> server. So I brought it down just to 15. 

I'd jack it up to 150 :)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null