/[monit]/monit/CHANGES.txt
ViewVC logotype

Diff of /monit/CHANGES.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.75 by hauk, Mon Aug 4 07:52:11 2003 UTC revision 1.76 by martinp, Wed Aug 6 15:03:24 2003 UTC
# Line 94  Version 4.0 Line 94  Version 4.0
94     not send alert message with bare line feeds anymore. Thanks to Rail     not send alert message with bare line feeds anymore. Thanks to Rail
95     Aliev <rail@iqchoice.com>     Aliev <rail@iqchoice.com>
96    
97    *  Checksum and timestamp statements are now restricted to new file
98       and directory monitoring services types. Usage of these statements
99       is obsolete from this release. To test checksum ot timestamp, you
100       should use file or directory check service and define dependency
101       of the process on this check service. See documentation and
102       UPGRADE.txt for syntax.
103    
104    *  You don't need to specify path to the file or directory in checksum
105       or timestamp statements. It is inherited from parent check service.
106       See documentation and UPGRADE.txt for syntax.
107    
108  *  The timestamp statement is extended to check for file and directory  *  The timestamp statement is extended to check for file and directory
109     changes. You can now use the timestamp statement to get an alert if     changes. You can now use the timestamp statement to get an alert if
110     a file was changed. For instance:     a file was changed. For instance:
111       if timestamp /etc/passwd was changed then alert       check file passwd with path /etc/passwd
112           if timestamp was changed then alert
113     The timestamp does only test the last modified stamp not if the     The timestamp does only test the last modified stamp not if the
114     content of the file was changed. Use the checksum statement for     content of the file was changed. Use the checksum statement for
115     this.     this.
116    
117  *  The timestamp and resource statement now supports an optional exec  *  The timestamp, resource and size statement now supports an optional
118     statement. The exec statement is used to execute an arbitrary     exec statement. The exec statement is used to execute an arbitrary
119     program as an action for the resource or timestamp statement. For     program as an action for the resource, size or timestamp statement.
120     instance to restart apache if the httpd.conf file was changed:     For instance to restart apache if the httpd.conf file was changed:
121      if timestamp /usr/local/apache/conf/httpd.conf was changed       check file httpd.conf with path /usr/local/apache/conf/httpd.conf
122        then exec "/etc/init.d/apache restart"         if timestamp was changed then exec "/etc/init.d/apache restart"
123    
124  *  This release changes the port statement to explicit require an  *  This release changes the port statement to explicit require an
125     action to be executed upon a failed connection test. The port     action to be executed upon a failed connection test. The port
126     statement has also been extended to include an optional socket     statement has also been extended to include an optional socket
127     connection timeout.     connection timeout.
128    
129    *  Checksum statement bugfix. Previous versions compared only
130       first 31 characters of 32 possible.
131    
132    
133  Version 3.2  Version 3.2
134    

Legend:
Removed from v.1.75  
changed lines
  Added in v.1.76

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26