...
Configuration items
NMIS runs a daemon to periodically obtain periodically the nodes information, and other maintenance jobs that needs need to be done (to calculate metrics, cleanup jobs, run the plugins, etc.).
The main process - the nmis scheduler - runs a loop and check checks which jobs needs need to be done. It will add these jobs into a queue, and it will instantiate forks fork worker processes that will run these jobs.
...
This means the maximum number of forks worker processes that the nmis main process will be able to start.
...
| Code Block |
|---|
'nmisd_worker_cycle' => 30, 'nmisd_worker_max_cycles' => 5100, |
nmisd_worker_cycle will set up is the number of seconds the process will sleep if it doesn't have any job to perform.
Every time a worker performs a job, a cycle counter is increased. It is possible to change the default behaviour so the worker is killed every N cycles. Another process will be started by the parent once the child process reaches the max cycles, if the number of children processes doesn't reach the max_workers. It will prevent a worker memory get too big. This number can be adjusted, as, if it is too low, there is a cost associated in killing and starting a new process. Can be changed in nmisd_worker_max_cycles. Check
for more details in tests with this value. Jira server Opmantek Support serverId 53b13e12-126f-35af-9131-52e658b644f5 key OMK-8536
Go to usr/local/nmis9/conf/ Config.nmis
