From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH] monit: Update to 5.28.1 Date: Wed, 04 Aug 2021 16:27:30 +0200 Message-ID: <5863CB68-6007-49F4-ACB7-A39E3579A0F7@ipfire.org> In-Reply-To: <20210731075712.2767-1-matthias.fischer@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3515304984649501448==" List-Id: --===============3515304984649501448== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you! Reviewed-by: Michael Tremer > On 31 Jul 2021, at 09:57, Matthias Fischer = wrote: >=20 > For details see: > https://mmonit.com/monit/changes/ >=20 > New: Issue #979: If filesystem mount flags changed, show both old > and new value. Originally only the new value was reported. >=20 > Fixed: Issue #960: The memory usage may report wrong value if system > memory size changed after Monit start. The problem was frequent > on KVM/LXC containers where MemTotal is dynamicaly updated. >=20 > Fixed: Issue #965: Monit CLI: if a custom configuration file was > used with the -c option, and the file cannot be read by Monit, > an AssertException was thrown. Monit will report normal error > instead of the exception now. >=20 > Fixed: Issue #966: Monit CLI: The service name pattern was changed > to case-sensitive in Monit 5.28.0. Revert the behaviour back > to case-insensitive. >=20 > Fixed: Issue #971: The LINK UP and LINK DOWN tests now support short > form of the optional ELSE condition, in addition to the verbose ELSE > IF form. >=20 > Fixed: Issue #976: The space free test recovery always reported > value in percent, regardless of the test setting. If the test uses > absolute limit, Monit will report absolute space usage now. >=20 > Fixed: Issue #986: Services checks with custom schedule (the EVERY > statement) did set the data collection timestamp even if the > monitoring was skipped in the given cycle. The timestamp is now > updated only when the check was performed. >=20 > Fixed: Issue #990: Monit built with libressl may crash during > verification of the expired SSL certificate. >=20 > Fixed: Issue #968: Systemd and upstart templates: templates used > to set the path to the configuration file in the sysconfdir, which > is optionally set via the configure script during the compilation. > The path wasn't fully expanded in the template though, so it was > invalid. The template doesn't specify the explicit path now and lets > Monit search for the configuration file in all supported locations > (including the sysconfdir). >=20 > Changed: Issue #984: The permission check of the SSL PEM key file > allows group read permissions now (originally Monit enforced that > the file is readable only by the file owner). >=20 > Signed-off-by: Matthias Fischer > --- > lfs/monit | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) >=20 > diff --git a/lfs/monit b/lfs/monit > index 3720995cd..06306eb8f 100644 > --- a/lfs/monit > +++ b/lfs/monit > @@ -24,7 +24,7 @@ >=20 > include Config >=20 > -VER =3D 5.28.0 > +VER =3D 5.28.1 >=20 > THISAPP =3D monit-$(VER) > DL_FILE =3D $(THISAPP).tar.gz > @@ -32,7 +32,7 @@ DL_FROM =3D $(URL_IPFIRE) > DIR_APP =3D $(DIR_SRC)/$(THISAPP) > TARGET =3D $(DIR_INFO)/$(THISAPP) > PROG =3D monit > -PAK_VER =3D 14 > +PAK_VER =3D 15 >=20 > DEPS =3D >=20 > @@ -44,7 +44,7 @@ objects =3D $(DL_FILE) >=20 > $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE) >=20 > -$(DL_FILE)_MD5 =3D 778ac383dea002a5cf2330dffcc65660 > +$(DL_FILE)_MD5 =3D 832783145cbd523bd6bc2c36e0e5c052 >=20 > install : $(TARGET) >=20 > --=20 > 2.18.0 >=20 --===============3515304984649501448==--