/[monit]/monit/web/monit.html
ViewVC logotype

Diff of /monit/web/monit.html

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

revision 1.25 by hauk, Fri Sep 19 03:44:17 2003 UTC revision 1.26 by hauk, Sat Sep 20 03:25:04 2003 UTC
# Line 4  Line 4 
4  <LINK REV="made" HREF="mailto:bhcompile@daffy.perf.redhat.com">  <LINK REV="made" HREF="mailto:bhcompile@daffy.perf.redhat.com">
5  </HEAD>  </HEAD>
6    
7  <BODY>  <BODY bgcolor="#FFFFFF">
8    
9  <A NAME="__index__"></A>  <A NAME="__index__"></A>
10  <!-- INDEX BEGIN -->  <!-- INDEX BEGIN -->
# Line 174  action and exit without transforming its Line 174  action and exit without transforming its
174  <P><STRONG>stop name</STRONG>  <P><STRONG>stop name</STRONG>
175     Stop the named service and disable its monitoring.     Stop the named service and disable its monitoring.
176     The name is a service entry name from the monitrc     The name is a service entry name from the monitrc
177     file. available</P>     file.</P>
178  <P><STRONG>restart all</STRONG>  <P><STRONG>restart all</STRONG>
179     Stop and start <EM>all</EM> services. If the group option     Stop and start <EM>all</EM> services. If the group option
180     is set, only restart the services in the named group.</P>     is set, only restart the services in the named group.</P>
# Line 184  action and exit without transforming its Line 184  action and exit without transforming its
184  <P><STRONG>monitor all</STRONG>      <P><STRONG>monitor all</STRONG>    
185     Enable monitoring of all services listed in the     Enable monitoring of all services listed in the
186     control file. If the group option is set, only start     control file. If the group option is set, only start
187     the services monitoring in the named group.</P>     monitoring of services in the named group.</P>
188  <P><STRONG>monitor name</STRONG>  <P><STRONG>monitor name</STRONG>
189     Enable monitoring of the named service.  The name is     Enable monitoring of the named service.  The name is
190     a service entry name from the monitrc file. Monit will     a service entry name from the monitrc file. Monit will
# Line 249  Comments begin with a # and extend throu Line 249  Comments begin with a # and extend throu
249  There are three kinds of tokens in the control file: grammar  There are three kinds of tokens in the control file: grammar
250  keywords, numbers and strings.</P>  keywords, numbers and strings.</P>
251  <P>On a semantic level, the control file consists of two types of  <P>On a semantic level, the control file consists of two types of
252  entries:</P>  statements:</P>
253  <OL>  <OL>
254  <LI><STRONG><A NAME="item_Global_set%2Dstatements">Global set-statements</A></STRONG><BR>  <LI><STRONG><A NAME="item_Global_set%2Dstatements">Global set-statements</A></STRONG><BR>
255    
# Line 306  various statements will be explained in Line 306  various statements will be explained in
306  <P>monit will log status and error messages to a log file. If  <P>monit will log status and error messages to a log file. If
307  <STRONG>syslog</STRONG> is given as a value for the <EM>-l</EM> command-line switch  <STRONG>syslog</STRONG> is given as a value for the <EM>-l</EM> command-line switch
308  (or the keyword <EM>set logfile syslog</EM> is found in the control  (or the keyword <EM>set logfile syslog</EM> is found in the control
309  file) monit will use the <STRONG>syslog</STRONG> system daemon for logging  file) monit will use the <STRONG>syslog</STRONG> system daemon to log
310  messages. To turn off logging, simply do not set the logfile in  messages. To turn off logging, simply do not set the logfile in
311  the control file (and of course, do not use the -l switch)</P>  the control file (and of course, do not use the -l switch)</P>
312  <P>  <P>
# Line 341  of waking it up.</P> Line 341  of waking it up.</P>
341  <HR>  <HR>
342  <H1><A NAME="init support">INIT SUPPORT</A></H1>  <H1><A NAME="init support">INIT SUPPORT</A></H1>
343  <P>Monit can run and be controlled from <EM>init</EM>. If monit should  <P>Monit can run and be controlled from <EM>init</EM>. If monit should
344  crash <EM>init</EM> will re-spawn a new monit process. Using init to  crash, <EM>init</EM> will re-spawn a new monit process. Using init to
345  start monit is probably the best way to run monit if you want to  start monit is probably the best way to run monit if you want to
346  be certain that you always have a running monit daemon on your  be certain that you always have a running monit daemon on your
347  system. (It's obvious, but never the less worth to stress; Make  system. (It's obvious, but never the less worth to stress; Make
348  sure that the control file does not have any syntax errors before  sure that the control file does not have any syntax errors before
349  you start monit from init. Also, make sure that if you run monit  you start monit from init. Also, make sure that if you run monit
350  from init, that you do not start monit in your startup scripts as  from init, that you do not start monit from a startup scripts as
351  well).</P>  well).</P>
352  <P>To setup monit to run from init, you can either use the 'set  <P>To setup monit to run from init, you can either use the 'set
353  init' statement in monit's control file or use the -I option from  init' statement in monit's control file or use the -I option from
# Line 365  the following command to re-examine /etc Line 365  the following command to re-examine /etc
365  For systems without telinit:</PRE>  For systems without telinit:</PRE>
366  <PRE>  <PRE>
367    kill -1 1</PRE>    kill -1 1</PRE>
368  <P>In the case, that you are using SYSV init script for starting the  <P><STRONG>Things you need to know if you choose to start monit from
369  monitored services and monit (either from init or rc its own rc  init:</STRONG> If monit is used to monitor services that are also started
370  script), in the special case of slow starting monitored service  at boot time (e.g. services started via SYSV init rc scripts or
371  you can observe the race condition between particular service's  via inittab) then in some situations a special race condition can
372  startup and its monitoring. In such case monit can produce false  occur. That is; if a service is slow to start, monit can assume
373  alarms. Possible solutions:</P>  that the service is not running and possibly try to start it and
374    raise an alert, while, in fact the service is already about to
375    start or already in its startup sequence. If you experience this
376    problem, here are a couple of strategies you can use to prevent
377    this type of race condition:</P>
378  <DL>  <DL>
379  <DT><STRONG><A NAME="item_start_critical_services_from_monit_directly%3A">start critical services from monit directly:</A></STRONG><BR>  <DT><STRONG><A NAME="item_start_critical_services_directly_from_monit%3A">start critical services directly from monit:</A></STRONG><BR>
380  <DD>  <DD>
381  This is the recommended solution - monit will takeover the  This is the recommended solution - let monit takeover the
382  responsibility for service's startup. To use it you need to  responsibility for starting services. To use this strategy you
383  replace the service's start and stop in appropriate runlevels.  must turn off the systems automatic start and stop for all
384  You can use for example on RedHat:  services handled by monit.
385    <P>On RedHat, you can for example use:</P>
386  <PRE>  <PRE>
387    chkconfig myprocess off</PRE>    chkconfig myprocess off</PRE>
388  <P>on Debian:</P>  <P>on Debian:</P>
389  <PRE>  <PRE>
390    update-rc.d -f myprocess remove</PRE>    update-rc.d -f myprocess remove</PRE>
391  <P>general example:</P>  <P>a general example:</P>
392  <PRE>  <PRE>
393    mv /etc/rc2.d/S99myprocess /etc/rc2.d/s99myprocess</PRE>    mv /etc/rc2.d/S99myprocess /etc/rc2.d/s99myprocess</PRE>
394  <P>To stop the service on system shutdown, you need either to add  <P>If monit is started from a rc script, then to stop the service at
395  for example following line to monit's rc script:</P>  systems shutdown, you should add the following line to monit's rc
396    script:</P>
397  <PRE>  <PRE>
398    /usr/local/bin/monit -c /etc/monitrc stop myprocess</PRE>    /usr/local/bin/monit -c /etc/monitrc stop myprocess</PRE>
399  <P>or to stop all services:</P>  <P>or if monit handles more than one service, simply stop all
400    services by using:</P>
401  <PRE>  <PRE>
402    /usr/local/bin/monit -c /etc/monitrc stop all</PRE>    /usr/local/bin/monit -c /etc/monitrc stop all</PRE>
403  <P>If you are running monit from init then you can add the second  <P>If monit instead is started from init then, add a second line to
404  line of following example to stop the service:</P>  inittab to stop the service:</P>
405  <PRE>  <PRE>
406    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc
407    m0:06:wait:/usr/local/bin/monit -Ic /etc/monitrc stop myprocess</PRE>    m0:06:wait:/usr/local/bin/monit -Ic /etc/monitrc stop myprocess</PRE>
408  <P>or to stop all services:</P>  <P>or to stop all services handled by monit:</P>
409  <PRE>  <PRE>
410    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc
411    m0:06:wait:/usr/local/bin/monit -Ic /etc/monitrc stop all</PRE>    m0:06:wait:/usr/local/bin/monit -Ic /etc/monitrc stop all</PRE>
412  <P>The monitored service must have start and stop methods defined,  <P>Services handled by monit <EM>must</EM> have start and stop methods
413  such as for example:</P>  defined so monit can start and stop a service. For instance:</P>
414  <PRE>  <PRE>
415    check process myprocess with pidfile /var/run/myprocess.pid    check process myprocess with pidfile /var/run/myprocess.pid
416          start program = &quot;/etc/init.d/myprocess start&quot;          start program = &quot;/etc/init.d/myprocess start&quot;
417          stop program = &quot;/etc/init.d/myprocess stop&quot;          stop program = &quot;/etc/init.d/myprocess stop&quot;
418          alert foo@bar.baz</PRE>          alert foo@bar.baz</PRE>
419  <P></P>  <P></P>
420  <DT><STRONG><A NAME="item_wait_for_service_to_start">wait for service to start</A></STRONG><BR>  <DT><STRONG><A NAME="item_make_init_wait_for_a_service_to_start%3A">make init wait for a service to start:</A></STRONG><BR>
421  <DD>  <DD>
422  This solution will cause that init process will wait for the service  This solution will make the init process wait for the service to
423  to start before it will continue to start other services. If you are  start before it will continue to start other services. If you are
424  running monit from init, you must define monit's line as last in  running monit from init, you must enter monit's line at the end
425  /etc/inittab (short example):  of /etc/inittab (A short example):
426  <PRE>  <PRE>
427    si::sysinit:/etc/init.d/rcS    si::sysinit:/etc/init.d/rcS
428    ...    ...
429    l2:2:wait:/etc/init.d/rc 2    l2:2:wait:/etc/init.d/rc 2
430    ...    ...
431    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc</PRE>    mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc</PRE>
432  <P>The rc script of the monitored service must be modified so, that it  <P>The rc script for the monitored service must be <EM>modified</EM> so,
433  will not return unless the service will be online or the startup  that it will not return unless the service was started or start
434  timed out. As dumb method sleep is sufficient.</P>  of the service timed out. Creative use of <CODE>sleep(1)</CODE> may be
435  <P>The monitored service must have start and stop methods defined,  sufficient.</P>
436  such as for example:</P>  <P>As in the above example, services handled by monit must have
437    start and stop methods defined, such as for example:</P>
438  <PRE>  <PRE>
439    check process myprocess with pidfile /var/run/myprocess.pid    check process myprocess with pidfile /var/run/myprocess.pid
440          start program = &quot;/etc/init.d/myprocess start&quot;          start program = &quot;/etc/init.d/myprocess start&quot;
441          stop program = &quot;/etc/init.d/myprocess stop&quot;          stop program = &quot;/etc/init.d/myprocess stop&quot;
442          alert foo@bar.baz</PRE>          alert foo@bar.baz</PRE>
443  <P></P>  <P></P>
444  <DT><STRONG><A NAME="item_enable_the_service_monitoring_manualy">enable the service monitoring manualy</A></STRONG><BR>  <DT><STRONG><A NAME="item_enable_the_service_monitoring_manually_from_monit%">enable the service monitoring manually from monit:</A></STRONG><BR>
445  <DD>  <DD>
446  <PRE>  <PRE>
447    check file myprocess.pid with path /var/run/myprocess.pid    check file myprocess.pid with path /var/run/myprocess.pid
# Line 447  such as for example:</P> Line 455  such as for example:</P>
455          stop program = &quot;/etc/init.d/myprocess stop&quot;          stop program = &quot;/etc/init.d/myprocess stop&quot;
456          alert foo@bar.baz          alert foo@bar.baz
457          mode manual</PRE>          mode manual</PRE>
458  <P>This will cause to wait for 5 minutes before it will enable  <P>This will cause monit to wait for 5 minutes before it will enable
459  monitoring of the service myprocess.</P>  monitoring of the service myprocess.</P>
460  </DL>  </DL>
461  <P>  <P>
# Line 665  for messages sent by monit, like so:</P> Line 673  for messages sent by monit, like so:</P>
673  <H1><A NAME="service timeout">SERVICE TIMEOUT</A></H1>  <H1><A NAME="service timeout">SERVICE TIMEOUT</A></H1>
674  <P><STRONG>monit</STRONG> provides a service timeout mechanism for situations  <P><STRONG>monit</STRONG> provides a service timeout mechanism for situations
675  where a service simply refuses to start or respond over a longer  where a service simply refuses to start or respond over a longer
676  period. In cases like this, and particularly if monits poll-cycle  period. In cases like this, and particularly if monit's poll-cycle
677  is low, monit will simply increase the machine load by trying to  is low, monit will simply increase the machine load by trying to
678  restart the service.</P>  restart the service.</P>
679  <P>The timeout mechanism monit provides is based on two variables,  <P>The timeout mechanism monit provides is based on two variables,
# Line 728  e.g. 'monit monitor apache'. Line 736  e.g. 'monit monitor apache'.
736  <LI>  <LI>
737  <STRONG>EXEC</STRONG> may be used to execute an arbitrary program <EM>and</EM> send  <STRONG>EXEC</STRONG> may be used to execute an arbitrary program <EM>and</EM> send
738  an alert. If you choose this action you must state the program to  an alert. If you choose this action you must state the program to
739  be executed. You may also optionally specify the uid and gid the  be executed and if the program require arguments you must enclose
740  executed program should switch to upon start. For instance:  the program and its arguments in a quoted string. You may
741    optionally specify the uid and gid the executed program should
742    switch to upon start. For instance:
743  <PRE>  <PRE>
744   exec &quot;/usr/local/tomcat/bin/startup.sh&quot;   exec &quot;/usr/local/tomcat/bin/startup.sh&quot;
745        as uid nobody and gid nobody</PRE>        as uid nobody and gid nobody</PRE>
746  <P>This may be useful if the program to be started cannot change to  <P>This may be useful if the program to be started cannot change to
747  a lesser privileged user and group. This is typically needed for  a lesser privileged user and group. This is typically needed for
748  Java Servers. If monit is run by the superuser, the program monit  Java Servers. Remember, if monit is run by the superuser, then
749  execute will be started with superuser privileges unless the uid  all programs executed by monit will be started with superuser
750  and gid extension was used.</P>  privileges unless the uid and gid extension was used.</P>
751  <P></P>  <P></P>
752  <LI>  <LI>
753  <STRONG>UNMONITOR</STRONG> will disable monitoring of the service <EM>and</EM> send  <STRONG>UNMONITOR</STRONG> will disable monitoring of the service <EM>and</EM> send
# Line 819  but instead use the string you submit. F Line 829  but instead use the string you submit. F
829      expect the sum 8f7f419955cefa0b33a2ba316cba3659      expect the sum 8f7f419955cefa0b33a2ba316cba3659
830   then alert</PRE>   then alert</PRE>
831  <P>You can, for example, use the GNU utility <EM>md5sum(1)</EM> to create  <P>You can, for example, use the GNU utility <EM>md5sum(1)</EM> to create
832  a checksum string for a file and then use this string in the  a checksum string for a file and use this string in the
833  expect-statement.</P>  expect-statement.</P>
834  <P><EM>action</EM> is a choice of ``ALERT'', ``RESTART'', ``STOP'', ``EXEC'' or  <P><EM>action</EM> is a choice of ``ALERT'', ``RESTART'', ``STOP'', ``EXEC'' or
835  ``UNMONITOR''</P>  ``UNMONITOR''</P>
# Line 830  illustrate this for the apache web serve Line 840  illustrate this for the apache web serve
840  <PRE>  <PRE>
841   check file httpd.conf path /usr/local/apache/conf/httpd.conf   check file httpd.conf path /usr/local/apache/conf/httpd.conf
842       if failed checksum       if failed checksum
843          then exec &quot;/usr/local/apache/bin/apachectl restart&quot;</PRE>          then exec &quot;/usr/local/apache/bin/apachectl graceful&quot;</PRE>
844  <P>If you plan to use the checksum statement for security reasons,  <P>If you plan to use the checksum statement for security reasons,
845  (a very good idea, by the way) and to monitor a file or files  (a very good idea, by the way) and to monitor a file or files
846  which should not change, then please read the DEPENDENCY TREE  which should not change, then please also read the DEPENDENCY
847  section below to see a detailed example on how to do this  TREE section below to see a detailed example on how to do this
848  properly.</P>  properly.</P>
849  <P>  <P>
850  <H2><A NAME="timestamp testing">TIMESTAMP TESTING</A></H2>  <H2><A NAME="timestamp testing">TIMESTAMP TESTING</A></H2>
# Line 981  size is explicitly defined (Note that th Line 991  size is explicitly defined (Note that th
991         if size != 95564 then exec &quot;/sbin/ifconfig eth0 down&quot;</PRE>         if size != 95564 then exec &quot;/sbin/ifconfig eth0 down&quot;</PRE>
992  <P>  <P>
993  <H2><A NAME="space testing">SPACE TESTING</A></H2>  <H2><A NAME="space testing">SPACE TESTING</A></H2>
994  <P>Monit can test devices/filesystems and check for space  <P>Monit can test devices/file systems and check for space
995  usage. This test may only be used within a device service entry  usage. This test may only be used within a device service entry
996  in the monit control file.</P>  in the monit control file.</P>
997  <P>Monit will check a device's total space usage. If you only want  <P>Monit will check a device's total space usage. If you only want
# Line 1279  process entry:</P> Line 1289  process entry:</P>
1289         if failed port 21 and protocol ftp then alert         if failed port 21 and protocol ftp then alert
1290         alert foo@bar.baz</PRE>         alert foo@bar.baz</PRE>
1291  <P>Since we did not explicit specify a host in the above test, monit  <P>Since we did not explicit specify a host in the above test, monit
1292  will connect to port 21 at ftp.redhat.com. Aprops, the host  will connect to port 21 at ftp.redhat.com. Apropos, the host
1293  address can be specified as a dotted IP address string or as  address can be specified as a dotted IP address string or as
1294  hostname in the DNS. The following is exactly[*] the same test,  hostname in the DNS. The following is exactly[*] the same test,
1295  but using an ip address instead:</P>  but were an ip address is used instead:</P>
1296  <PRE>  <PRE>
1297   check host up2date with address 66.187.232.30   check host up2date with address 66.187.232.30
1298         if failed port 21 and protocol ftp then alert         if failed port 21 and protocol ftp then alert
# Line 1378  commands. (That is; most of the availabl Line 1388  commands. (That is; most of the availabl
1388   'monit -g groupname monitor all'   'monit -g groupname monitor all'
1389   'monit -g groupname unmonitor all'</PRE>   'monit -g groupname unmonitor all'</PRE>
1390  <P>If a monit daemon is running in the background we will ask the  <P>If a monit daemon is running in the background we will ask the
1391  deamon (via the HTTP protocol) to execute the above commands.  daemon (via the HTTP protocol) to execute the above commands.
1392  That is, the daemon is requested to start and stop the services.  That is, the daemon is requested to start and stop the services.
1393  This ensures that a daemon will not restart a service that you  This ensures that a daemon will not restart a service that you
1394  requested to stop and that (any) timeout lock will be removed  requested to stop and that (any) timeout lock will be removed
# Line 1396  to connect to the server. You can add as Line 1406  to connect to the server. You can add as
1406  to, but only hosts with a valid domain name or its IP address are  to, but only hosts with a valid domain name or its IP address are
1407  allowed. If you specify a hostname that does not resolve, monit  allowed. If you specify a hostname that does not resolve, monit
1408  will write an error message in the console and not start.</P>  will write an error message in the console and not start.</P>
1409  <P>The http server will query a nameserver to check any hosts  <P>The http server will query a name server to check any hosts
1410  connecting to the server. If a host (client) is trying to connect  connecting to the server. If a host (client) is trying to connect
1411  to the server, but cannot be found in the access list or cannot  to the server, but cannot be found in the access list or cannot
1412  be resolved, the server will shutdown the connection to the  be resolved, the server will shutdown the connection to the
# Line 1407  client promptly.</P> Line 1417  client promptly.</P>
1417        allow localhost        allow localhost
1418        allow my.other.work.machine.com        allow my.other.work.machine.com
1419        allow 10.1.1.1</PRE>        allow 10.1.1.1</PRE>
1420    <P>Clients, not mentioned in the allow list that tries to connect to
1421    the server are logged with their ip-address.</P>
1422  <P>  <P>
1423  <H4><A NAME="basic authentication">Basic Authentication</A></H4>  <H4><A NAME="basic authentication">Basic Authentication</A></H4>
1424  <P>This authentication schema is HTTP specific and described in more  <P>This authentication schema is HTTP specific and described in more
# Line 1448  readable and writable for the user runni Line 1460  readable and writable for the user runni
1460  password is written in clear-text. (Use this command, /bin/chmod  password is written in clear-text. (Use this command, /bin/chmod
1461  600 ~/.monitrc). In fact, since monit <STRONG>version 3.0</STRONG>, monit will  600 ~/.monitrc). In fact, since monit <STRONG>version 3.0</STRONG>, monit will
1462  complain and exit if the control file is readable by others.</P>  complain and exit if the control file is readable by others.</P>
1463    <P>Clients trying to connect to the server but supply the wrong
1464    username and/or password are logged with their ip-address.</P>
1465  <P>  <P>
1466  <HR>  <HR>
1467  <H1><A NAME="dependency tree">DEPENDENCY TREE</A></H1>  <H1><A NAME="dependency tree">DEPENDENCY TREE</A></H1>
# Line 1620  file or a directory which is part of a f Line 1634  file or a directory which is part of a f
1634  recommended to use a block special file directly (for example  recommended to use a block special file directly (for example
1635  /dev/hda1 on Linux or /dev/dsk/c0t0d0s1 on Solaris, etc.) If you  /dev/hda1 on Linux or /dev/dsk/c0t0d0s1 on Solaris, etc.) If you
1636  use a mount point (for example /data), be careful, because if the  use a mount point (for example /data), be careful, because if the
1637  device is unmounted the test will still be true becasue the mount  device is unmounted the test will still be true because the mount
1638  point exist.  point exist.
1639  <P>If the device becomes unavailable, monit will call the entry's  <P>If the device becomes unavailable, monit will call the entry's
1640  start method if defined. if &lt;path&gt; does not point to a device,  start method if defined. if &lt;path&gt; does not point to a device,
# Line 1909  sent).</P> Line 1923  sent).</P>
1923         if failed port 443 with timeout 15 seconds then restart</PRE>         if failed port 443 with timeout 15 seconds then restart</PRE>
1924  <P>This example demonstrate how you can run a program as a specified  <P>This example demonstrate how you can run a program as a specified
1925  user (uid) and with a specified group (gid). Many daemon programs  user (uid) and with a specified group (gid). Many daemon programs
1926  will do the uid and gid switch by themself, but for those  will do the uid and gid switch by them self, but for those
1927  programs that does not (e.g. java programs), monit's ability to  programs that does not (e.g. java programs), monit's ability to
1928  start a program as a certain user can be very useful.  In this  start a program as a certain user can be very useful.  In this
1929  example we start the Tomcat Java Servlet Engine as the standard  example we start the Tomcat Java Servlet Engine as the standard
# Line 2332  and <EM>only</EM> the following environm Line 2346  and <EM>only</EM> the following environm
2346  <DL>  <DL>
2347  <DT><STRONG><A NAME="item_MONIT_EVENT">MONIT_EVENT</A></STRONG><BR>  <DT><STRONG><A NAME="item_MONIT_EVENT">MONIT_EVENT</A></STRONG><BR>
2348  <DD>  <DD>
2349  The event that occured on the service  The event that occurred on the service
2350  <P></P>  <P></P>
2351  <DT><STRONG><A NAME="item_MONIT_SERVICE">MONIT_SERVICE</A></STRONG><BR>  <DT><STRONG><A NAME="item_MONIT_SERVICE">MONIT_SERVICE</A></STRONG><BR>
2352  <DD>  <DD>
2353  The name of the service (from monitrc) on which the event occured.  The name of the service (from monitrc) on which the event occurred.
2354  <P></P>  <P></P>
2355  <DT><STRONG><A NAME="item_MONIT_DATE">MONIT_DATE</A></STRONG><BR>  <DT><STRONG><A NAME="item_MONIT_DATE">MONIT_DATE</A></STRONG><BR>
2356  <DD>  <DD>
2357  The time and date (rfc 822 style) the event occured  The time and date (rfc 822 style) the event occurred
2358  <P></P>  <P></P>
2359  <DT><STRONG><A NAME="item_MONIT_HOST">MONIT_HOST</A></STRONG><BR>  <DT><STRONG><A NAME="item_MONIT_HOST">MONIT_HOST</A></STRONG><BR>
2360  <DD>  <DD>
2361  The host the event occured on  The host the event occurred on
2362  <P></P></DL>  <P></P></DL>
2363  <P>The following environment variables are only available for  <P>The following environment variables are only available for
2364  process service entries:</P>  process service entries:</P>

Legend:
Removed from v.1.25  
changed lines
  Added in v.1.26

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