Fw: fork() problem?

[Richard Wu]

Hi, mike:
 
If you want the nagios to be run in parallel, set the value to 0, look at the nagios.cfg comments on the max_concurrent_checks. Here is the contnet:
# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized.  A value of 0
# will not restrict the number of concurrent checks that are
# being executed.
 
max_concurrent_checks=0

Richard Wu 
-----Original Message-----
From: Mike Culbertson [mailto:mike at omnipod.com]
Sent: Monday, October 21, 2002 1:41 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Fw: fork() problem?



Update on this.  I was little hasty in saying that setting the max_concurrent_checks restrained the forking.  I see now that, even when the var is set at 10, I now have 29 nagios procs running (my initial assumption that this var controlled forking is incorrect, sorry):
 
[root at machine nagios]# ps -ef | grep nagios | wc -l
     29
[root at machine nagios]# 
 
Also to clarify, I have taken into account the system being busy (it is).  But after a weekend of unattended running, there were 1968 nagios procs waiting for me this morning, which I am assuming probably isn't normal :)  Thanks again.
 
Mike C

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20021021/9e793353/attachment.html>