From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZQZN42Dx3z332R for ; Sun, 30 Mar 2025 13:09:08 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZQZN05TCpz2xMD for ; Sun, 30 Mar 2025 13:09:04 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZQZN00v5HzX5; Sun, 30 Mar 2025 13:09:04 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1743340144; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Gs+hSXKJLF9iMd0CeCGEHXPrDJ3/H8fcowbL5QlP518=; b=ABcOvPaKH/OBgAkOcMLsa6/uQ7xlnu4kuxgD/TAJzvFUXnwwORuQ0BQsSfdw/uv0uQSiWd YxlTp+iZDZ+sE6Aw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1743340144; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Gs+hSXKJLF9iMd0CeCGEHXPrDJ3/H8fcowbL5QlP518=; b=QkhFl2sl9sZuvs212F48t9XpVphz+D4IT3Jan//rWhNf6pXeZJNwsebp9H4eVBEteX/RKK edbmwFOiAC1q9nL0U0BJygyq3Esn6hySywomgdbpkeuMHOcajfix4O7UDXSyx7+49rraRL q+VzDjlp1IfyE0NSuXODf/3i5P6mjAlMZcNd/NPLBcpU9IBy6BxhvsVnqX7HQxlrHSmxI5 SvTdGhnNHDzQGtX0t5cpVNKC3f5fQNdIcWv041h6c0R3BSxHtnMUDZNpxE1S4TQ3CUGXKs cW+yOeusD2PeYsTdFTTODfLhK/RWl2WQRkXOPXUyQIwnCKaA0Vm2UHctPH7Arw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: [PATCH 1/2] zabbix_agentd: Update to 7.0.11 (LTS) From: Michael Tremer In-Reply-To: <243162f261210936b03956e5a2e64f407c250240.camel@disroot.org> Date: Sun, 30 Mar 2025 14:09:03 +0100 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20250327224552.3963717-1-robin.roevens@disroot.org> <243162f261210936b03956e5a2e64f407c250240.camel@disroot.org> To: Robin Roevens Hello, > On 28 Mar 2025, at 23:53, Robin Roevens = wrote: >=20 > Hi Michael >=20 > Michael Tremer schreef op vr 28-03-2025 om 13:55 [+0000]: >> Thank you. I merged this. >>=20 > Thanks! >=20 >> Do we need to add an extra note to the change log so that people are >> aware of this breaking change? >>=20 > That is not a bad idea, possibly not every IPFire user is active on = the > forum and some thus may have missed the survey. So please do. >=20 > As you will, or maybe already have noticed, I redid/corrected my last > patch where I set the number of agent forks to 0 on new installations. > It is now set to 3 in my newest patch, which was the default in > previous Zabbix agent versions. > I will add an upgrade note about that in the IPFire wiki zabbix_agentd > addon page.=20 > Maybe that is also worth mentioning in the blog post: that users with > an existing zabbix_agentd installation may also want to lower the > number of forks the agent starts, especially when running it on a mini > appliance; with a link to that wiki page. I think the Mini appliance is one of the more powerful pieces of = hardware that people are using=E2=80=A6 I have merged the patch. Thank you! -Michael > Regards > Robin >=20 >> -Michael >>=20 >>> On 27 Mar 2025, at 22:45, Robin Roevens >>> wrote: >>>=20 >>> - Update from version 6.0.33 to 7.0.11 >>> - Update of rootfile not required >>>=20 >>> This is a major release update to the next LTS version and breaks >>> compatibility with Zabbix Server 6.x. >>> A survey on the forum resulted in nobody claiming to still use >>> Zabbix Server v6.x. >>>=20 >>> Full changelogs: >>> - https://www.zabbix.com/rn/rn7.0.0 >>> - https://www.zabbix.com/rn/rn7.0.1 >>> - https://www.zabbix.com/rn/rn7.0.2 >>> - https://www.zabbix.com/rn/rn7.0.3 >>> - https://www.zabbix.com/rn/rn7.0.4 >>> - https://www.zabbix.com/rn/rn7.0.5 >>> - https://www.zabbix.com/rn/rn7.0.6 >>> - https://www.zabbix.com/rn/rn7.0.7 >>> - https://www.zabbix.com/rn/rn7.0.8 >>> - https://www.zabbix.com/rn/rn7.0.9 >>> - https://www.zabbix.com/rn/rn7.0.10 >>> - https://www.zabbix.com/rn/rn7.0.11 >>>=20 >>> Signed-off-by: Robin Roevens >>> --- >>> lfs/zabbix_agentd | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >>>=20 >>> diff --git a/lfs/zabbix_agentd b/lfs/zabbix_agentd >>> index bd81dba22..dbe2088fb 100644 >>> --- a/lfs/zabbix_agentd >>> +++ b/lfs/zabbix_agentd >>> @@ -26,7 +26,7 @@ include Config >>>=20 >>> SUMMARY =3D Zabbix Agent >>>=20 >>> -VER =3D 6.0.37 >>> +VER =3D 7.0.11 >>>=20 >>> THISAPP =3D zabbix-$(VER) >>> DL_FILE =3D $(THISAPP).tar.gz >>> @@ -34,7 +34,7 @@ DL_FROM =3D $(URL_IPFIRE) >>> DIR_APP =3D $(DIR_SRC)/$(THISAPP) >>> TARGET =3D $(DIR_INFO)/$(THISAPP) >>> PROG =3D zabbix_agentd >>> -PAK_VER =3D 16 >>> +PAK_VER =3D 17 >>>=20 >>> DEPS =3D fping >>>=20 >>> @@ -48,7 +48,7 @@ objects =3D $(DL_FILE) >>>=20 >>> $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE) >>>=20 >>> -$(DL_FILE)_BLAKE2 =3D >>> 6bf65efe59963294699d8fc6b6456167ae035c075f057c6ca85c612cc41f3f812b1 >>> 4189ed7e03ab2446e751720f8908f8e098fc0fd7335f95251b221b66b674a >>> +$(DL_FILE)_BLAKE2 =3D >>> 0c6544c64febc51e6fc153863b46e333d9d5564c83f40b71362a15c0533d48e50e5 >>> c340b35b2ca0dd1d776d0452f4aae42dc44d4e0e4b2c5949df02efbc7fc06 >>>=20 >>> install : $(TARGET) >>>=20 >>> --=20 >>> 2.49.0 >>>=20 >>>=20 >>> --=20 >>> Dit bericht is gescanned op virussen en andere gevaarlijke >>> inhoud door MailScanner en lijkt schoon te zijn. >>>=20 >>>=20 >>=20 >>=20 >=20 >=20 > --=20 > Dit bericht is gescanned op virussen en andere gevaarlijke > inhoud door MailScanner en lijkt schoon te zijn.