nagios -s info [Was: fast reboot]

[jeff vier]

On Fri, 2004-01-16 at 16:48, Neil wrote:
> Why is it that my recommended value for max_concurrent_checks is just 9? Can 
> it be because, I am running it on a low end machine with low memory? 

Dunno.  Possibly.
My machine is a dual 1.4Ghz Intel (PIII) with a gig of ram.

And here's my nagios.cfg (stripped of comments, blank lines, and
non-performance stuff), if you're curious:
(run 'grep -v "^#" nagios.cfg |grep -v "^$' to get this)
-------------
check_external_commands=1
command_check_interval=5s
log_rotation_method=d
use_syslog=0
log_notifications=1
log_service_retries=0
log_host_retries=0
log_event_handlers=0
log_initial_states=1
log_external_commands=1
log_passive_service_checks=1
inter_check_delay_method=s
service_interleave_factor=s
max_concurrent_checks=150
service_reaper_frequency=15
sleep_time=1
service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30
ocsp_timeout=5
perfdata_timeout=5
retain_state_information=1
retention_update_interval=14
use_retained_program_state=1
interval_length=60
use_agressive_host_checking=0
execute_service_checks=1
accept_passive_service_checks=1
enable_notifications=1
enable_event_handlers=1
process_performance_data=1
obsess_over_services=0
check_for_orphaned_services=1
check_service_freshness=1
freshness_check_interval=300
aggregate_status_updates=0
status_update_interval=15
enable_flap_detection=0
low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0
---------



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