[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[monit-dev] [monit] r352 committed - 5.2.5
|
From: |
monit |
|
Subject: |
[monit-dev] [monit] r352 committed - 5.2.5 |
|
Date: |
Mon, 28 Mar 2011 18:21:41 +0000 |
Revision: 352
Author: address@hidden
Date: Mon Mar 28 11:20:50 2011
Log: 5.2.5
http://code.google.com/p/monit/source/detail?r=352
Modified:
/trunk/contrib/packages/redhat/monit.spec
/trunk/doc/monit.html
=======================================
--- /trunk/contrib/packages/redhat/monit.spec Wed Feb 23 02:11:48 2011
+++ /trunk/contrib/packages/redhat/monit.spec Mon Mar 28 11:20:50 2011
@@ -1,6 +1,6 @@
Name: monit
Summary: Process monitor and restart utility
-Version: 5.2.4
+Version: 5.2.5
Release: 1
Source: http://www.mmonit.com/monit/dist/%{name}-%{version}.tar.gz
Group: Utilities/Console
@@ -58,6 +58,9 @@
%{_mandir}/man1/%{name}.1.gz
%changelog
+* Wed Mar 28 2011 Martin Pala <address@hidden>
+- Upgraded to monit-5.2.5
+
* Wed Feb 23 2011 Martin Pala <address@hidden>
- Upgraded to monit-5.2.4
=======================================
--- /trunk/doc/monit.html Wed Jan 19 10:40:32 2011
+++ /trunk/doc/monit.html Mon Mar 28 11:20:50 2011
@@ -4,7 +4,7 @@
<head>
<title>Monit - utility for monitoring services on a Unix system</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<link rev="made" href="mailto:address@hidden"; />
+<link rev="made" href="mailto:address@hidden"; />
</head>
<body style="background-color: white">
@@ -250,6 +250,11 @@
Check all services listed in the control file. This
action is also the default behavior when Monit runs
in daemon mode.</p>
+<p><strong>procmatch regex</strong>
+ Allows for easy testing of pattern for process match
+ check. The command takes regular expression as an
+ argument and displays all running processes matching
+ the pattern.</p>
<p>
</p>
<hr />
@@ -824,7 +829,6 @@
--------------------
ALERT | "alert"
EXEC | "exec"
- MONITOR | "monitor"
RESTART | "restart"
START | "start"
STOP | "stop"
@@ -1095,10 +1099,6 @@
extension was used.</p>
</li>
<li>
-<p><strong>MONITOR</strong> will enable monitoring of the service
<em>and</em> send
-an alert.</p>
-</li>
-<li>
<p><strong>UNMONITOR</strong> will disable monitoring of the service
<em>and</em> send
an alert. The service will not be checked by Monit anymore nor
restarted again later. To reactivate monitoring of the service
@@ -1119,7 +1119,7 @@
</dl>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>Example:</p>
<pre>
check file with path /cifs/mydata
@@ -1178,7 +1178,7 @@
specify a <em>unit</em>. This could be "%" or if applicable
"B" (Byte),
"kB" (1024 Byte), "MB" (1024 KiloByte) or
"GB" (1024 MegaByte).</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>To calculate the cycles, a counter is raised whenever the
expression above is true and it is lowered whenever it is false
(but not below 0). All counters are reset in case of a restart.</p>
@@ -1225,7 +1225,7 @@
<em>sha1sum(1)</em> to create a checksum string for a file and
use this string in the expect-statement.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The checksum statement in variable form may be used to check a
file for changes and if changed, do a specified action. For
instance to reload a server if its configuration file was
@@ -1270,7 +1270,7 @@
<p><em>unit</em> is either "SECOND", "MINUTE",
"HOUR" or "DAY" (it is also
possible to use "SECONDS", "MINUTES",
"HOURS", or "DAYS").</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The variable timestamp statement is useful for checking a file
for changes and then execute an action. This version was written
particularly with configuration files in mind. For instance, if
@@ -1347,7 +1347,7 @@
"byte", "kilobyte", "megabyte",
"gigabyte". If it is not
specified, "byte" unit is assumed by default.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The variable size test form is useful for checking a file for
changes and send an alert or execute an action. Monit will
register the size of the file at startup and monitor the file for
@@ -1413,7 +1413,7 @@
<p><em>path</em> is an absolute path to a file containing extended
regular expression on every line. See also <code>regex(7)</code>.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>You can use the <em>NOT</em> statement to invert a match.</p>
<p>The content is only being checked every cycle. If content is
being added and removed between two checks they are unnoticed.</p>
@@ -1462,7 +1462,7 @@
</dl>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>Example:</p>
<pre>
check filesystem rootfs with path /
@@ -1497,7 +1497,7 @@
alternatives "byte", "kilobyte", "megabyte",
"gigabyte",
"percent".</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>
</p>
<h2><a name="inode_testing">INODE TESTING</a></h2>
@@ -1524,7 +1524,7 @@
count of inodes. You can use the "%" character or the longer
alternative "percent" as a unit.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>
</p>
<h2><a name="permission_testing">PERMISSION TESTING</a></h2>
@@ -1543,7 +1543,7 @@
can omit the leading zeros, Monit will add the zeros to the left
thus for example "640" is valid value and matches
"0640").</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The web interface will show a permission warning if the test
failed.</p>
<p>We recommend that you use the UNMONITOR action in a permission
@@ -1570,7 +1570,7 @@
</dl>
<p><em>user</em> defines a user id either in numeric or in string form.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The web interface will show a uid warning if the test should
fail.</p>
<p>We recommend that you use the UNMONITOR action in a uid
@@ -1597,7 +1597,7 @@
</dl>
<p><em>user</em> defines a group id either in numeric or in string
form.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>The web interface will show a gid warning if the test should
fail.</p>
<p>We recommend that you use the UNMONITOR action in a gid
@@ -1622,7 +1622,7 @@
</dl>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>This test is useful to detect possible process restarts which has
occurred in the timeframe between two Monit testing cycles. In
the case that the restart was fast and the process provides
@@ -1652,7 +1652,7 @@
</dl>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>This test is useful for detecting changes of a process parent.</p>
<p>Example:</p>
<pre>
@@ -1882,7 +1882,7 @@
connection failed and execute the specified action. The default
connect timeout is 5 seconds.</p>
<p><em>action</em> is a choice of "ALERT", "RESTART",
"START", "STOP",
-"EXEC", "MONITOR" or "UNMONITOR".</p>
+"EXEC" or "UNMONITOR".</p>
<p>
</p>
<h4><a name="connection_testing_using_the_url_notation">Connection testing
using the URL notation</a></h4>
@@ -2595,11 +2595,13 @@
defined.
<regex> is alternative process specification using pattern matching
to process name (command line) from process table instead of pidfile.
-The pattern to match can be obtained using 'ps' utility. The first
-match is used so this form of check is useful for unique pattern
-matching - the pidfile should be used where possible as it defines
-expected pid exactly (pattern matching won't be useful for Apache
-in most cases for example).
+The first match is used so this form of check is useful for unique
+pattern matching - the pidfile should be used where possible as it
+defines expected pid exactly (pattern matching won't be useful for
+Apache in most cases for example).
+The pattern can be obtained using <em>monit procmatch ".*"</em>
CLI command
+which lists all processes visible to Monit or using the <em>ps</em>
utility.
+The "procmatch" CLI command can be used to test your pattern as
well.
If Monit runs in passive mode or the start methods is not defined,
Monit will just send alerts on errors.</p>
</li>
@@ -2653,7 +2655,7 @@
</li>
<li><strong><a name="check_system_unique_name" class="item">CHECK SYSTEM
<unique name></a></strong>
-<p>The system name is usualy hostname, but any descriptive name can be
+<p>The system name is usually hostname, but any descriptive name can be
used. This test allows to check general system resources such as
CPU usage (percent of time spent in user, system and wait), total
memory usage or load average.</p>
@@ -2956,7 +2958,7 @@
for a process restart is to first execute the stop-program, wait
up to 30s for the process to stop and then execute the start-program
and wait up to 30s for it to start. The length of start or stop
-timeout can be overriden using the 'timeout' option. If Monit was
+timeout can be overridden using the 'timeout' option. If Monit was
unable to stop or start the service a failed alert message will
be sent if you have requested alert messages to be sent.</p>
<pre>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [monit-dev] [monit] r352 committed - 5.2.5,
monit <=