4 |
|
|
5 |
Version 4.0 |
Version 4.0 |
6 |
|
|
7 |
BUGFIXES: |
NEW FEATURES AND FUNCTIONS |
|
* Monit now closes all file descriptors before spawning a child |
|
|
processes. There was a problem with open file descriptors inherited |
|
|
by processes started under monit's control. Thanks to Peter |
|
|
Holdaway <pholdaway@technocom-wireless.com> for reporting the |
|
|
problem. |
|
|
|
|
|
* This release fixes a problem with alert messages and qmail. Qmail |
|
|
complained about bare line feeds in some alert messages. Monit does |
|
|
not send alert message with bare line feeds anymore. Thanks to Rail |
|
|
Aliev <rail@iqchoice.com> |
|
|
|
|
|
* Fixed the bug that did not report actions on a service unless a |
|
|
start statement was defined for the service. Now it is possible get |
|
|
notification via email if a service died, even if you did not |
|
|
include any start statement. For instance, this is now a complete |
|
|
statement and will, report if the service apache should die: |
|
|
check process apache with pidfile /usr/local/apache/logs/httpd.pid |
|
|
alert foo@bar.baz |
|
|
|
|
|
* Fixed a bug in the lexer that required the start and stop statement |
|
|
to use SPACE '=' "/<path> argument" when arguments was used. The |
|
|
start and stop statement can now be written as: |
|
|
start "/<path>/program start" if you want to. |
|
|
|
|
|
* Checksum statement bug fix. Previous versions compared only |
|
|
first 31 characters of 32 possible. |
|
|
|
|
|
* This release utilize a state file to save significant process data. |
|
|
This allows data to be persistent and survive a monit reload and |
|
|
let monit recover from a crash and pick up without losing the |
|
|
process state. |
|
|
|
|
|
INCOMPATIBLE EXTENSIONS AND CHANGES (ORIGINAL SYNTAX CHANGED): |
|
|
* The service names are no longer restricted by reserved names. |
|
|
Due to this, the syntax of DEPENDS was changed. |
|
|
|
|
|
* The syntax of resource monitoring has changed. "CPUUSAGE", |
|
|
"MEMUSAGE", "MEMKBYTE" is dropped in favor of the unit based |
|
|
"MEM" and "CPU" commands. Please consult the man page for |
|
|
details. |
|
|
|
|
|
* The syntax for the checksum statement has changed so the statement |
|
|
is a real IF-THEN statement. An example of a valid checksum |
|
|
statement: "if failed checksum then stop". The old syntax version |
|
|
is obsolete. |
|
|
|
|
|
* The syntax for the timeout statement has changed so the statement |
|
|
is a real IF-THEN statement. An example of a valid timeout |
|
|
statement is: |
|
|
if 2 restarts within 3 cycles then timeout |
|
|
The old syntax version, e.g. timeout(2, 3) still works but is |
|
|
deprecated and future releases may remove this version. |
|
|
|
|
|
* This release changes the port statement to explicit require an |
|
|
action to be executed upon a failed connection test. The port |
|
|
statement has also been extended to include an optional socket |
|
|
connection timeout. |
|
|
|
|
|
* The checksum statement is now restricted to a check file service |
|
|
entry. Usage of this statement in a check process service is |
|
|
obsolete from this release. See the documentation and the |
|
|
UPGRADE.txt file accompanying the software. |
|
|
|
|
|
* The timestamp statement is now restricted to a check file service |
|
|
entry. Usage of this statement in a check process service is |
|
|
obsolete from this release. See the documentation and the |
|
|
UPGRADE.txt file accompanying the software. |
|
|
|
|
|
* You do not need to specify the path to the file or directory in a |
|
|
checksum or in a timestamp statements. The path is inherited from |
|
|
the parent check service. See the documentation and UPGRADE.txt |
|
|
file. |
|
|
|
|
|
* The command line arguments start, stop and restart needs a |
|
|
following 'all' from this release on to start/stop/restart *all* |
|
|
programs in the control file. For instance 'monit stop all'. This |
|
|
is done to avoid that an accidentally user input error should stop |
|
|
every monitored service at once. |
|
|
|
|
|
* The $PROGRAM tag in the mail-format statement was renamed to |
|
|
$SERVICE. The meaning is the same - it is replaced by the name of |
|
|
the monitored service, but compared to previous versions these |
|
|
services can now be either program, device, directory or file. The |
|
|
$PROGRAM tag is still supported for backward compatibility, but use |
|
|
of $SERVICE is highly recommended because it is more relevant. |
|
|
|
|
|
EXTENSIONS: |
|
8 |
* A new check service entry was added to allow monitoring of devices. |
* A new check service entry was added to allow monitoring of devices. |
9 |
In addition to common options Monit is able to watch permission, |
In addition to common options Monit is able to watch permission, |
10 |
owner's uid and gid, space and inodes and execute customized actions |
owner's uid and gid, space and inodes and execute customized actions |
106 |
* HP/UX support brought to the same state like all other operating |
* HP/UX support brought to the same state like all other operating |
107 |
systems. |
systems. |
108 |
|
|
109 |
|
BACKWARD INCOMPATIBLE CHANGES |
110 |
|
* The service names are no longer restricted by reserved names. |
111 |
|
Due to this, the syntax of DEPENDS was changed. |
112 |
|
|
113 |
|
* The syntax of resource monitoring has changed. "CPUUSAGE", |
114 |
|
"MEMUSAGE", "MEMKBYTE" is dropped in favor of the unit based |
115 |
|
"MEM" and "CPU" commands. Please consult the man page for |
116 |
|
details. |
117 |
|
|
118 |
|
* The syntax for the checksum statement has changed so the statement |
119 |
|
is a real IF-THEN statement. An example of a valid checksum |
120 |
|
statement: "if failed checksum then stop". The old syntax version |
121 |
|
is obsolete. |
122 |
|
|
123 |
|
* The syntax for the timeout statement has changed so the statement |
124 |
|
is a real IF-THEN statement. An example of a valid timeout |
125 |
|
statement is: |
126 |
|
if 2 restarts within 3 cycles then timeout |
127 |
|
The old syntax version, e.g. timeout(2, 3) still works but is |
128 |
|
deprecated and future releases may remove this version. |
129 |
|
|
130 |
|
* This release changes the port statement to explicit require an |
131 |
|
action to be executed upon a failed connection test. The port |
132 |
|
statement has also been extended to include an optional socket |
133 |
|
connection timeout. |
134 |
|
|
135 |
|
* The checksum statement is now restricted to a check file service |
136 |
|
entry. Usage of this statement in a check process service is |
137 |
|
obsolete from this release. See the documentation and the |
138 |
|
UPGRADE.txt file accompanying the software. |
139 |
|
|
140 |
|
* The timestamp statement is now restricted to a check file service |
141 |
|
entry. Usage of this statement in a check process service is |
142 |
|
obsolete from this release. See the documentation and the |
143 |
|
UPGRADE.txt file accompanying the software. |
144 |
|
|
145 |
|
* You do not need to specify the path to the file or directory in a |
146 |
|
checksum or in a timestamp statements. The path is inherited from |
147 |
|
the parent check service. See the documentation and UPGRADE.txt |
148 |
|
file. |
149 |
|
|
150 |
|
* The command line arguments start, stop and restart needs a |
151 |
|
following 'all' from this release on to start/stop/restart *all* |
152 |
|
programs in the control file. For instance 'monit stop all'. This |
153 |
|
is done to avoid that an accidentally user input error should stop |
154 |
|
every monitored service at once. |
155 |
|
|
156 |
|
* The $PROGRAM tag in the mail-format statement was renamed to |
157 |
|
$SERVICE. The meaning is the same - it is replaced by the name of |
158 |
|
the monitored service, but compared to previous versions these |
159 |
|
services can now be either program, device, directory or file. The |
160 |
|
$PROGRAM tag is still supported for backward compatibility, but use |
161 |
|
of $SERVICE is highly recommended because it is more relevant. |
162 |
|
|
163 |
|
BUGFIXES: |
164 |
|
* Monit now closes all file descriptors before spawning a child |
165 |
|
processes. There was a problem with open file descriptors inherited |
166 |
|
by processes started under monit's control. Thanks to Peter |
167 |
|
Holdaway <pholdaway@technocom-wireless.com> for reporting the |
168 |
|
problem. |
169 |
|
|
170 |
|
* This release fixes a problem with alert messages and qmail. Qmail |
171 |
|
complained about bare line feeds in some alert messages. Monit does |
172 |
|
not send alert message with bare line feeds anymore. Thanks to Rail |
173 |
|
Aliev <rail@iqchoice.com> |
174 |
|
|
175 |
|
* Fixed the bug that did not report actions on a service unless a |
176 |
|
start statement was defined for the service. Now it is possible get |
177 |
|
notification via email if a service died, even if you did not |
178 |
|
include any start statement. For instance, this is now a complete |
179 |
|
statement and will, report if the service apache should die: |
180 |
|
check process apache with pidfile /usr/local/apache/logs/httpd.pid |
181 |
|
alert foo@bar.baz |
182 |
|
|
183 |
|
* Fixed a bug in the lexer that required the start and stop statement |
184 |
|
to use SPACE '=' "/<path> argument" when arguments was used. The |
185 |
|
start and stop statement can now be written as: |
186 |
|
start "/<path>/program start" if you want to. |
187 |
|
|
188 |
|
* Checksum statement bug fix. Previous versions compared only |
189 |
|
first 31 characters of 32 possible. |
190 |
|
|
191 |
|
* This release utilize a state file to save significant process data. |
192 |
|
This allows data to be persistent and survive a monit reload and |
193 |
|
let monit recover from a crash and pick up without losing the |
194 |
|
process state. |
195 |
|
|
196 |
|
|
197 |
Version 3.2 |
Version 3.2 |
198 |
|
|