[PATCH] zabbix_agentd: Set passive check agents to 3 by default

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

Hi again

Sorry for the spam, but it seems I made a mistake by setting the number
of Zabbix agent forks to 0 in my last patch.

TLDR; That change breaks the monitoring of OpenVPN Clients in the Zabbix
monitoring template I provide and promote on the IPFire wiki.

After upgrading to Zabbix Agent v7 I noticed it forking 10 instances on
my mini appliance (old version) in contrary to only 3 instances on
previous versions of Zabbix agent, and I wrongly thought my monitoring 
template for it is only using active checks, so I concluded that we simply
don't need passive checks unless a user decides otherwise.
But I forgot that for monitoring OpenVPN clients, my template generates
new hosts (one for each client) on the Zabbix Server, all pointing to the 
same IPFire instance. But those hosts representing OpenVPN clients won't
receive the results of their checks if they are set to active, since
active checks relies on the hostname of the IPFire instance to be the
same as the hostname set in the Zabbix Server. And that is not the case
for those OpenVPN clients.

Regards
Robin

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