projected or recommended service check option

[Neil]

Hey guys,
I don't know why this email bounced back to my inbox. So I am sending it 
again. 

I tried nagios -s nagios.cfg and it gives me this info. 

SERVICE SCHEDULING INFORMATION
     -------------------------------
     Total services:             76
     Total hosts:                44 

     Command check interval:     5 sec
     Check reaper interval:      10 sec 

     Inter-check delay method:   SMART
     Average check interval:     247.895 sec
     Inter-check delay:          3.262 sec 

     Interleave factor method:   SMART
     Average services per host:  1.727
     Service interleave factor:  2 

     Initial service check scheduling info:
     --------------------------------------
     First scheduled check:      1075330870 -> Wed Jan 28 15:01:10 2004
     Last scheduled check:       1075331114 -> Wed Jan 28 15:05:14 2004 

     Rough guidelines for max_concurrent_checks value:
     -------------------------------------------------
     Absolute minimum value:     4
     Recommend value:            12 


I don't know why I am just still having a 12 in recommended value. I already 
installed it on a 1 gig memory. And I am just monitoring 74 services for 
now.  What are the things that I need to tweak so I can have a good 
max_concurrent_checks value? 

If someone again can send there .cfg files, it will be awesome. This will 
give me an idea what things I am doing wrong. 

Thanks in advance. 


-------------------------------------------------------
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