public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] monit: Update to 5.28.1
Date: Wed, 04 Aug 2021 16:27:30 +0200	[thread overview]
Message-ID: <5863CB68-6007-49F4-ACB7-A39E3579A0F7@ipfire.org> (raw)
In-Reply-To: <20210731075712.2767-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3350 bytes --]

Thank you!

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 31 Jul 2021, at 09:57, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> For details see:
> https://mmonit.com/monit/changes/
> 
>    New: Issue #979: If filesystem mount flags changed, show both old
>    and new value. Originally only the new value was reported.
> 
>    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.
> 
>    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.
> 
>    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.
> 
>    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 <SUCCEEDED|FAILED> form.
> 
>    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.
> 
>    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.
> 
>    Fixed: Issue #990: Monit built with libressl may crash during
>    verification of the expired SSL certificate.
> 
>    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).
> 
>    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).
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/monit | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/monit b/lfs/monit
> index 3720995cd..06306eb8f 100644
> --- a/lfs/monit
> +++ b/lfs/monit
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 5.28.0
> +VER        = 5.28.1
> 
> THISAPP    = monit-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
> DIR_APP    = $(DIR_SRC)/$(THISAPP)
> TARGET     = $(DIR_INFO)/$(THISAPP)
> PROG       = monit
> -PAK_VER    = 14
> +PAK_VER    = 15
> 
> DEPS       =
> 
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 778ac383dea002a5cf2330dffcc65660
> +$(DL_FILE)_MD5 = 832783145cbd523bd6bc2c36e0e5c052
> 
> install : $(TARGET)
> 
> -- 
> 2.18.0
> 


           reply	other threads:[~2021-08-04 14:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210731075712.2767-1-matthias.fischer@ipfire.org>]

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=5863CB68-6007-49F4-ACB7-A39E3579A0F7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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