[PATCH] zabbix_agentd: Set passive check agents to 3 by default on new installations.

[Robin Roevens <robin.roevens@disroot.org>]

Zabbix Agent since v7 by default forks 10 instances to listen for and concurrently execute  incoming (passive) checks. This was only 3 in previous versions and should be plenty on an IPFire instance where resources can be scarce.

Users with an existing installation will have to manually add the parameter to their config if they don't want the Zabbix new default of 10 . This will be documented in the wiki.

Signed-off-by: Robin Roevens <robin.roevens@disroot.org>
---
 config/zabbix_agentd/zabbix_agentd.conf | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/config/zabbix_agentd/zabbix_agentd.conf b/config/zabbix_agentd/zabbix_agentd.conf
index a5a608d83..c9e041113 100644
--- a/config/zabbix_agentd/zabbix_agentd.conf
+++ b/config/zabbix_agentd/zabbix_agentd.conf
@@ -13,12 +13,13 @@
 Server=127.0.0.1
 ServerActive=127.0.0.1
 
-# Number of pre-forked instances of zabbix_agentd that process passive checks.
-# On IPFire this is set to 0 to disable passive checks and only allow active
-# checks by default.
-# Set this value in a range of 1-100 to enable passive checks or comment it
-# out to revert to the Zabbix agent default (10).
-StartAgents=0
+# Number of pre-forked instances of zabbix_agentd that concurrently process 
+# passive checks.
+# On IPFire this is by default set to 3 to minimize the required resources. 
+# This parameter can be increased up to 100 if you have a lot of slow-running
+# checks, and the agent acts as the bottleneck. 
+# Or set to 0 to disable passive checks.
+StartAgents=3
 
 # List of comma delimited IP addresses that the agent should listen on
 # for passive checks. 
-- 
2.49.0


-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.