monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[monit] [Announce] monit 5.0 beta2


From: Martin Pala
Subject: [monit] [Announce] monit 5.0 beta2
Date: Fri, 01 Aug 2008 00:02:50 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.15) Gecko/20080615 Iceape/1.1.10 (Debian-1.1.10-1)

Monit 5.0 beta2 is available:

Download from: http://tildeslash.com/monit/dist/beta/monit-5.0_beta2.tar.gz

MD5 checksum:    3d104ba47636b0c890e3c9427366a55d
SHA256 checksum: 7e2f9b4f61f44a45bb2955cb575e1bdb2aff55a3258056ed30a361f1160160c8
Change log:      http://www.tildeslash.com/monit/dist/beta/CHANGES.txt

This is a new features and bugfix release which has been tested on the
following platforms:

Debian 4.0             [x86]
FreeBSD 6.3            [x86]
FreeBSD 7.0            [x86]
Mac OS X 10.5.4        [ppc]
NetBSD 4.0             [x86]
OpenBSD 4.1            [x86]
CentOS 4.6             [x86]
CentOS 5.1             [x86]
Fedora 8               [x86]
Ubuntu 8.04            [x64]




Version 5.0 beta2:
------------------

BUGFIXES:
* HP-UX fixes and extensions, monit should run on HP-UX without
  problems, including cpu, memory and filesystem monitoring.
  Thanks to Brian Downey for support and help.

* Fixed #23467: Don't exit, only issue a warning if the "include"
  statement did not find any files to include.

* Fixed #23530: Event queue does not work with default of unlimited
  slots.

* Fixed #23617: The process cpu usage is initializing in the first
  cycle so the value is set to 0% - if the 'cpu usage < xyz%' test
  was used to check that the process usage is higher then given level,
  it was always true. Monit now skips the process cpu usage check
  in the first cycle.

* Make sure monit alerts has a unique message id. Thanks to Steve
  Purcell for report

* Fixed possible crash when monit is watching VPS environment on
  Linux which reports number of CPUs as 0. Thanks to Marius
  Schmidt for report.

* When service is unmonitored or stopped, cleanup the event
  states as well so when the monitoring is enabled again or
  service started, no reactions to old ad possibly obsolete
  events will be send.



Finally, a big thanks to ALL who have contributed work and time to
create this release.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]