From: Alex Koch <ipfire@starkstromkonsument.de>
To: development@lists.ipfire.org
Subject: [PATCH] zabbix_agentd: Update to 4.2.6
Date: Sun, 01 Sep 2019 23:34:58 +0200 [thread overview]
Message-ID: <20190901213458.22220-1-ipfire@starkstromkonsument.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
Release Notes: https://www.zabbix.com/rn/rn4.2.6
Signed-off-by: Alex Koch <ipfire(a)starkstromkonsument.de>
---
config/zabbix_agentd/zabbix_agentd.conf | 12 ++++++++----
lfs/zabbix_agentd | 6 +++---
2 files changed, 11 insertions(+), 7 deletions(-)
diff --git a/config/zabbix_agentd/zabbix_agentd.conf b/config/zabbix_agentd/zabbix_agentd.conf
index 07f71c184..21b8e0122 100644
--- a/config/zabbix_agentd/zabbix_agentd.conf
+++ b/config/zabbix_agentd/zabbix_agentd.conf
@@ -305,8 +305,12 @@ LoadModulePath=/usr/lib/zabbix
### Option: LoadModule
# Module to load at agent startup. Modules are used to extend functionality of the agent.
-# Format: LoadModule=<module.so>
-# The modules must be located in directory specified by LoadModulePath.
+# Formats:
+# LoadModule=<module.so>
+# LoadModule=<path/module.so>
+# LoadModule=</abs_path/module.so>
+# Either the module must be located in directory specified by LoadModulePath or the path must precede the module name.
+# If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.
# It is allowed to include multiple LoadModule parameters.
#
# Mandatory: no
@@ -353,14 +357,14 @@ LoadModulePath=/usr/lib/zabbix
# TLSCRLFile=
### Option: TLSServerCertIssuer
-# Allowed server certificate issuer.
+# Allowed server certificate issuer.
#
# Mandatory: no
# Default:
# TLSServerCertIssuer=
### Option: TLSServerCertSubject
-# Allowed server certificate subject.
+# Allowed server certificate subject.
#
# Mandatory: no
# Default:
diff --git a/lfs/zabbix_agentd b/lfs/zabbix_agentd
index d4d5a22fb..8aac4d000 100644
--- a/lfs/zabbix_agentd
+++ b/lfs/zabbix_agentd
@@ -24,7 +24,7 @@
include Config
-VER = 4.2.1
+VER = 4.2.6
THISAPP = zabbix-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = zabbix_agentd
-PAK_VER = 3
+PAK_VER = 4
DEPS = ""
###############################################################################
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = e55ba94060ba2548ae8a1c29fd7cb7dd
+$(DL_FILE)_MD5 = 6cd55cd743d416d9ffbf2e6fdee680ee
install : $(TARGET)
--
2.17.1
next reply other threads:[~2019-09-01 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:34 Alex Koch [this message]
2019-09-02 11:34 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190901213458.22220-1-ipfire@starkstromkonsument.de \
--to=ipfire@starkstromkonsument.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox