From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] monit: Update to 5.29.0
Date: Mon, 20 Sep 2021 17:10:17 +0200
Message-ID: <373e91ed-4f6e-403e-cc2d-77540db6f630@ipfire.org>
In-Reply-To: <15c64079-7e06-a860-1f0f-189c46480bec@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1257827991480073826=="
List-Id: <development.lists.ipfire.org>

--===============1257827991480073826==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On 20.09.2021 15:45, Adolf Belka wrote:
> Hi Matthias,

Hi Adolf,

> You missed the increment of the PAK_VER number.

Erm...DOH!...Done.

I've sent a fix - hoping this will be enough,

Best,
Matthias

> Regards,
>=20
> Adolf.
>=20
> On 18/09/2021 16:11, Matthias Fischer wrote:
>> For details see:
>> https://mmonit.com/monit/changes/
>>
>>      New: Issue #715: The PostgreSQL protocol test has been improved and
>>      now supports authentication with username, password and database
>>      when testing connection. Example:
>>
>>      if failed port 5432
>>          protocol pgsql username "username" password "12345" database "tes=
t"
>>      then alert
>>
>>      Previous Monit versions used hardcoded credentials when testing
>>      connection to postgresql (user=3Droot and database=3Droot). This could
>>      trigger thousands of messages like this in the postgresql log:
>>
>>      root(a)root FATAL:  password authentication failed for user "root"
>>      root(a)root DETAIL:  Role "root" does not exist.
>>
>>      Note: Monit will continue to use the hardcoded credentials (for
>>      backward compatibility) unless username and password are set.
>>      New: Issue #973: You can now test program output using a regular
>>      expression. Syntax:
>>
>>      IF CONTENT [!]=3D <regex> THEN action
>>
>>      Example:
>>
>>      check program disk0_smart with path "/usr/sbin/nvme smart-log /dev/nv=
me0"
>>          if content !=3D "critical_warning[ ]+: 0" then alert
>>
>>      New: Issue #974: Monit CLI: Added support for the -g (group) option
>>      to the report command. Example:
>>
>>      monit -g database report
>>
>>      Fixed: Issue #991 (Monit 5.28.1 regression): MacOS: Monit didn't
>>      compile on MacOS 10.13 or older. Thanks to Lutz Mader.
>>
>>      Fixed: Issue #994 (Monit 5.28.1 regression): The check program
>>      statement with every did not work properly.
>>
>>      Fixed: Issue #995: Monit start delay was vulnerable to time jumps
>>      when Monit is waiting for the delay to pass. Thanks to Daniel Crowe.
>>
>>      Fixed: Issue #975: Monit CLI: Monit did not report a warning if -s,
>>      -p, -l, -g or -c command-line options were specified multiple times
>>      and silently used the last value only. Monit will generate a warning
>>      now.
>>
>>      Fixed: Issue #972: Monit GUI: The log view had no size limit when
>>      reading the Monit log file and could block the browser if the log
>>      file was large.
>>
>>      Fixed: Issue #955: If more than one every statement is used in
>>      a check-service context only the last value is (silently) used.
>>      We now report a warning in this case.
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>>   lfs/monit | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lfs/monit b/lfs/monit
>> index 06306eb8f..c01e5bab0 100644
>> --- a/lfs/monit
>> +++ b/lfs/monit
>> @@ -24,7 +24,7 @@
>>  =20
>>   include Config
>>  =20
>> -VER        =3D 5.28.1
>> +VER        =3D 5.29.0
>>  =20
>>   THISAPP    =3D monit-$(VER)
>>   DL_FILE    =3D $(THISAPP).tar.gz
>> @@ -44,7 +44,7 @@ objects =3D $(DL_FILE)
>>  =20
>>   $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE)
>>  =20
>> -$(DL_FILE)_MD5 =3D 832783145cbd523bd6bc2c36e0e5c052
>> +$(DL_FILE)_MD5 =3D 8a0546d0d52216b22ebd57acc0bb1e03
>>  =20
>>   install : $(TARGET)
>>  =20
>=20


--===============1257827991480073826==--