/[monit]/monit/monit.pod
ViewVC logotype

Diff of /monit/monit.pod

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

revision 1.167 by martinp, Sun Aug 14 08:44:48 2005 UTC revision 1.168 by martinp, Mon Sep 5 09:51:37 2005 UTC
# Line 467  monitored object changed. This involves: Line 467  monitored object changed. This involves:
467    
468   o A file checksum changed   o A file checksum changed
469   o A file size changed   o A file size changed
470     o A file content match
471   o A file/directory timestamp changed   o A file/directory timestamp changed
472    
473  You should use an alert statement to notify monit that you want  You should use an alert statement to notify monit that you want
# Line 571  The following alert-statement: Line 572  The following alert-statement:
572                  timeout                  timeout
573                  resource                  resource
574                  checksum                  checksum
575                    match
576                  timestamp                  timestamp
577                  connection                  connection
578                  permission}                  permission}
# Line 662  are fixed and are: Line 664  are fixed and are:
664   EVENT_GID        "GID failed"             "GID passed"   EVENT_GID        "GID failed"             "GID passed"
665   EVENT_ICMP       "ICMP failed"            "ICMP passed"   EVENT_ICMP       "ICMP failed"            "ICMP passed"
666   EVENT_INVALID    "Invalid type"           "Type passed"   EVENT_INVALID    "Invalid type"           "Type passed"
667     EVENT_MATCH      "Regex match"            "No regex match"
668   EVENT_NONEXIST   "Does not exist"         "Exists"   EVENT_NONEXIST   "Does not exist"         "Exists"
669   EVENT_PERMISSION "Permission failed"      "Permission passed"   EVENT_PERMISSION "Permission failed"      "Permission passed"
670   EVENT_RESOURCE   "Resource limit matched" "Resource limit passed"   EVENT_RESOURCE   "Resource limit matched" "Resource limit passed"
# Line 690  fixed and are: Line 693  fixed and are:
693    
694   ACTION_ALERT     "alert"   ACTION_ALERT     "alert"
695   ACTION_EXEC      "exec"   ACTION_EXEC      "exec"
696     ACTION_MONITOR   "monitor"
697   ACTION_RESTART   "restart"   ACTION_RESTART   "restart"
698   ACTION_START     "start"   ACTION_START     "start"
699   ACTION_STOP      "stop"   ACTION_STOP      "stop"
# Line 832  action. General format: Line 836  action. General format:
836    
837  =over 4  =over 4
838    
839  =item  IF <TEST> THEN ACTION [ELSE IF RECOVERED THEN ACTION]  =item  IF <TEST> [[<X>] [TIMES WITHIN] <Y> CYCLES] THEN ACTION
840           [ELSE IF RECOVERED [[<X>] [TIMES WITHIN] <Y> CYCLES] THEN ACTION]
841    
842  =back  =back
843    
# Line 842  remains true. The value for comparision Line 847  remains true. The value for comparision
847  action is evalueated only once (on failed->recovered state change  action is evalueated only once (on failed->recovered state change
848  only). The 'ELSE IF RECOVERED' part is optional - if omitted,  only). The 'ELSE IF RECOVERED' part is optional - if omitted,
849  monit will do alert action on recovery by default. The alert is  monit will do alert action on recovery by default. The alert is
850  delivered once on each state change regardless of state change  delivered only once on each state change unless overriden by
851  direction).  'reminder' alert option.
852    
853    
854  Variable object tests beggins with 'IF CHANGED' statement and  Variable object tests beggins with 'IF CHANGED' statement and
# Line 856  was changed.  Variable tests are support Line 861  was changed.  Variable tests are support
861  that other tests can be useful in variable form too, please let  that other tests can be useful in variable form too, please let
862  us know.  us know.
863    
864    
865  =over 4  =over 4
866    
867  =item  IF CHANGED <TEST> THEN ACTION  =item  IF CHANGED <TEST> [[<X>] [TIMES WITHIN] <Y> CYCLES] THEN ACTION
868    
869  =back  =back
870    
# Line 870  cycles. The alert is delivered each time Line 876  cycles. The alert is delivered each time
876  true.  true.
877    
878    
879    You can restrict the event ratio needed to change the state:
880    
881    =over 4
882    
883    =item  ... [[<X>] [TIMES WITHIN] <Y> CYCLES] ...
884    
885    =back
886    
887    This part is optional and is supported by all testing rules.
888    It defines how many event occurences during how many cycles
889    are needed to trigger the following action. You can use it
890    in several ways - the core syntax is:
891    
892     [<X>] <Y> CYCLES
893    
894    It is possible to use filling words which give the rule better
895    first-sight sense. You can use any filling words such as: FOR,
896    TIMES, WITHIN, thus for example:
897    
898     if failed port 80 for 3 times within 5 cycles then alert
899    
900    or
901    
902     if failed port 80 for 10 cycles then unmonitor
903    
904    When you don't specify the <X>, it equals to <Y> by default,
905    thus the rule applies when <Y> consecutive cycles of inverse
906    event occured (relatively to the current service state).
907    
908    When you omit it at all, monit will by default change state
909    on first inverse event, which is equivalent to this notation:
910    
911     1 times within 1 cycles
912    
913    It is possible to use this option for failed, passed/recovered
914    or changed rules. More complex examples:
915    
916     check device rootfs with path /dev/hda1
917      if space usage > 80% 5 times within 15 cycles then alert else if passed for 10 cycles then alert
918      if space usage > 90% for 5 cycles then exec '/try/to/free/the/space'
919      if space usage > 99% then exec '/stop/processess'
920    
921    Note that the maximal cycles count which can be used in the rule
922    is limited by the size of 'long long' data type on your platform.
923    This provides 64 cycles on usual platforms currently. In the case
924    that you use unsupported value, the configuration parser will
925    tell you the limits during monit startup.
926    
927    
928  You must select an action to be executed from this list:  You must select an action to be executed from this list:
929    
930  =over 4  =over 4
# Line 920  privileges unless the uid and gid extens Line 975  privileges unless the uid and gid extens
975    
976  =item *  =item *
977    
978    B<MONITOR> will enable monitoring of the service I<and> send
979    an alert.
980    
981    =item *
982    
983  B<UNMONITOR> will disable monitoring of the service I<and> send  B<UNMONITOR> will disable monitoring of the service I<and> send
984  an alert. The service will not be checked by monit anymore nor  an alert. The service will not be checked by monit anymore nor
985  restarted again later.  To reactivate monitoring of the service  restarted again later.  To reactivate monitoring of the service
986  you must explicitly enable monitoring from monit's web interface  you must explicitly enable monitoring from monit's web interface
987  or from the console using the monitor argument.  or from the console using the monitor argument.
988    
   
989  =back  =back
990    
991    
# Line 948  statements in [brackets]), Line 1007  statements in [brackets]),
1007    
1008  =over 4  =over 4
1009    
1010  =item IF resource operator value [cycles] THEN action  =item IF resource operator value [[<X>] <Y> CYCLES] THEN action
1011        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1012    
1013  =back  =back
1014    
# Line 983  CHILDREN). For CPU, MEMORY and TOTALMEMO Line 1042  CHILDREN). For CPU, MEMORY and TOTALMEMO
1042  I<unit>.  This could be "%" or if applicable "B" (Byte), "kB"  I<unit>.  This could be "%" or if applicable "B" (Byte), "kB"
1043  (1024 Byte), "MB" (1024 KiloByte) or "GB" (1024 MegaByte).  (1024 Byte), "MB" (1024 KiloByte) or "GB" (1024 MegaByte).
1044    
 I<cycles> is the maximum number of cycles the expression above  
 has to be true in order to start an action. To specify the number  
 of cycles you must state a number followed by the keyword CYCLES.  
 If I<cycles> is omitted then the default is one cycle.  
   
1045  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1046  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1047    
1048    
1049  To calculate the cycles, a counter is raised whenever the  To calculate the cycles, a counter is raised whenever the
# Line 1017  file does not change. Syntax (keywords a Line 1071  file does not change. Syntax (keywords a
1071    
1072  =over 4  =over 4
1073    
1074  =item IF FAILED [MD5|SHA1] CHECKSUM [EXPECT checksum] THEN action  =item IF FAILED [MD5|SHA1] CHECKSUM [EXPECT checksum] [[<X>] <Y> CYCLES] THEN action
1075        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1076    
1077  =back  =back
1078    
# Line 1027  file changes. Syntax (keywords are in ca Line 1081  file changes. Syntax (keywords are in ca
1081    
1082  =over 4  =over 4
1083    
1084  =item IF CHANGED [MD5|SHA1] CHECKSUM THEN action  =item IF CHANGED [MD5|SHA1] CHECKSUM [[<X>] <Y> CYCLES] THEN action
1085    
1086  =back  =back
1087    
# Line 1050  I<sha1sum(1)> to create a checksum strin Line 1104  I<sha1sum(1)> to create a checksum strin
1104  use this string in the expect-statement.  use this string in the expect-statement.
1105    
1106  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1107  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1108    
1109  The checksum statement in variable form may be used to check a  The checksum statement in variable form may be used to check a
1110  file for changes and if changed, do a specified action.  For  file for changes and if changed, do a specified action.  For
# Line 1083  timestamp conditions. Syntax (keywords a Line 1137  timestamp conditions. Syntax (keywords a
1137    
1138  =over 4  =over 4
1139    
1140  =item IF TIMESTAMP [[operator] value [unit]] THEN action  =item IF TIMESTAMP [[operator] value [unit]] [[<X>] <Y> CYCLES] THEN action
1141        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1142    
1143  =back  =back
1144    
# Line 1094  execute an action. Syntax (keywords are Line 1148  execute an action. Syntax (keywords are
1148    
1149  =over 4  =over 4
1150    
1151  =item IF CHANGED TIMESTAMP THEN action  =item IF CHANGED TIMESTAMP [[<X>] <Y> CYCLES] THEN action
1152    
1153  =back  =back
1154    
# Line 1109  I<unit> is either "SECOND", "MINUTE", "H Line 1163  I<unit> is either "SECOND", "MINUTE", "H
1163  possible to use "SECONDS", "MINUTES", "HOURS", or "DAYS").  possible to use "SECONDS", "MINUTES", "HOURS", or "DAYS").
1164    
1165  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1166  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1167    
1168    
1169  The variable timestamp statement is useful for checking a file for  The variable timestamp statement is useful for checking a file for
# Line 1178  size conditions. Syntax (keywords are in Line 1232  size conditions. Syntax (keywords are in
1232    
1233  =over 4  =over 4
1234    
1235  =item IF SIZE [[operator] value [unit]] THEN action  =item IF SIZE [[operator] value [unit]] [[<X>] <Y> CYCLES] THEN action
1236        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1237    
1238  =back  =back
1239    
# Line 1189  file for size changes and if changed, ex Line 1243  file for size changes and if changed, ex
1243    
1244  =over 4  =over 4
1245    
1246  =item IF CHANGED SIZE THEN action  =item IF CHANGED SIZE [[<X>] <Y> CYCLES] THEN action
1247    
1248  =back  =back
1249    
# Line 1205  I<unit> is a choice of "B","KB","MB","GB Line 1259  I<unit> is a choice of "B","KB","MB","GB
1259  specified, "byte" unit is assumed by default.  specified, "byte" unit is assumed by default.
1260    
1261  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1262  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1263    
1264    
1265  The variable size test form is useful for checking a file for  The variable size test form is useful for checking a file for
# Line 1273  an alarm is triggered.  Syntax (keywords Line 1327  an alarm is triggered.  Syntax (keywords
1327    
1328  =over 4  =over 4
1329    
1330  =item IF [NOT] MATCH {regex|path} THEN action  =item IF [NOT] MATCH {regex|path} [[<X>] <Y> CYCLES] THEN action
1331    
1332  =back  =back
1333    
# Line 1284  I<path> is an absolute path to a file co Line 1338  I<path> is an absolute path to a file co
1338  regular expression on every line. See also regex(7).  regular expression on every line. See also regex(7).
1339    
1340  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1341  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1342    
1343  You can use the I<NOT> statement to invert a match.  You can use the I<NOT> statement to invert a match.
1344    
# Line 1355  The full syntax for the space statement Line 1409  The full syntax for the space statement
1409    
1410  =over 4  =over 4
1411    
1412  =item IF SPACE operator value unit THEN action  =item IF SPACE operator value unit [[<X>] <Y> CYCLES] THEN action
1413        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1414    
1415  =back  =back
1416    
# Line 1370  alternatives "byte", "kilobyte", "megaby Line 1424  alternatives "byte", "kilobyte", "megaby
1424  "percent".  "percent".
1425    
1426  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1427  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1428    
1429    
1430    
# Line 1389  The syntax for the inode statement is: Line 1443  The syntax for the inode statement is:
1443    
1444  =over 4  =over 4
1445    
1446  =item IF INODE(S) operator value [unit] THEN action  =item IF INODE(S) operator value [unit] [[<X>] <Y> CYCLES] THEN action
1447        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1448    
1449  =back  =back
1450    
# Line 1404  count of inodes. You can use the "%" cha Line 1458  count of inodes. You can use the "%" cha
1458  alternative "percent" as a unit.  alternative "percent" as a unit.
1459    
1460  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1461  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1462    
1463    
1464    
# Line 1418  The syntax for the permission statement Line 1472  The syntax for the permission statement
1472    
1473  =over 4  =over 4
1474    
1475  =item IF FAILED PERM(ISSION) octalnumber THEN action  =item IF FAILED PERM(ISSION) octalnumber [[<X>] <Y> CYCLES] THEN action
1476        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1477    
1478  =back  =back
1479    
# Line 1428  I<octalnumber> defines permissions for a Line 1482  I<octalnumber> defines permissions for a
1482  device.  device.
1483    
1484  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1485  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1486    
1487    
1488  The web interface will show a permission warning if the test  The web interface will show a permission warning if the test
# Line 1459  The syntax for the uid statement is: Line 1513  The syntax for the uid statement is:
1513    
1514  =over 4  =over 4
1515    
1516  =item IF FAILED UID user THEN action  =item IF FAILED UID user [[<X>] <Y> CYCLES] THEN action
1517        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1518    
1519  =back  =back
1520    
1521  I<user> defines a user id either in numeric or in string form.  I<user> defines a user id either in numeric or in string form.
1522    
1523  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1524  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1525    
1526    
1527  The web interface will show a uid warning if the test should  The web interface will show a uid warning if the test should
# Line 1498  The syntax for the gid statement is: Line 1552  The syntax for the gid statement is:
1552    
1553  =over 4  =over 4
1554    
1555  =item IF FAILED GID user THEN action  =item IF FAILED GID user [[<X>] <Y> CYCLES] THEN action
1556        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1557    
1558  =back  =back
1559    
# Line 1507  The syntax for the gid statement is: Line 1561  The syntax for the gid statement is:
1561  I<user> defines a group id either in numeric or in string form.  I<user> defines a group id either in numeric or in string form.
1562    
1563  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1564  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1565    
1566    
1567  The web interface will show a gid warning if the test should  The web interface will show a gid warning if the test should
# Line 1541  The syntax for the pid statement is: Line 1595  The syntax for the pid statement is:
1595    
1596  =over 4  =over 4
1597    
1598  =item IF CHANGED PID THEN action  =item IF CHANGED PID [[<X>] <Y> CYCLES] THEN action
1599    
1600  =back  =back
1601    
1602  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1603  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1604    
1605  This test is useful to detect possible process restarts which  This test is useful to detect possible process restarts which
1606  has occured in the timeframe between two monit testing cycles.  has occured in the timeframe between two monit testing cycles.
# Line 1586  The syntax for the ppid statement is: Line 1640  The syntax for the ppid statement is:
1640    
1641  =over 4  =over 4
1642    
1643  =item IF CHANGED PPID THEN action  =item IF CHANGED PPID [[<X>] <Y> CYCLES] THEN action
1644    
1645  =back  =back
1646    
1647  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1648  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1649    
1650  This test is useful to detect possible process parent change.  This test is useful to detect possible process parent change.
1651  This may happen normaly only in the case that the process parent  This may happen normaly only in the case that the process parent
# Line 1627  as follows (keywords are in capital and Line 1681  as follows (keywords are in capital and
1681  =over 4  =over 4
1682    
1683  =item IF FAILED [host] port [type]  =item IF FAILED [host] port [type]
1684           [protocol|{send/expect}+] [timeout]           [protocol|{send/expect}+] [timeout] [[<X>] <Y> CYCLES]
1685        THEN action        THEN action
1686        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1687    
1688  =back  =back
1689    
# Line 1638  or for Unix sockets, Line 1692  or for Unix sockets,
1692  =over 4  =over 4
1693    
1694  =item  IF FAILED [unixsocket] [type]  =item  IF FAILED [unixsocket] [type]
1695            [protocol|{send/expect}+] [timeout]            [protocol|{send/expect}+] [timeout] [[<X>] <Y> CYCLES]
1696         THEN action         THEN action
1697        [ELSE IF RECOVERED THEN action]        [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1698    
1699  =back  =back
1700    
# Line 1783  connection failed and execute the specif Line 1837  connection failed and execute the specif
1837  connect timeout is 5 seconds.  connect timeout is 5 seconds.
1838    
1839  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",  I<action> is a choice of "ALERT", "RESTART", "START", "STOP",
1840  "EXEC" or "UNMONITOR".  "EXEC", "MONITOR" or "UNMONITOR".
1841    
1842    
1843  =head4 Connection testing using the URL notation  =head4 Connection testing using the URL notation
# Line 1797  in capital and optional statements in [b Line 1851  in capital and optional statements in [b
1851    
1852    IF FAILED URL ULR-spec    IF FAILED URL ULR-spec
1853       [CONTENT {==|!=} "regular-expression"]       [CONTENT {==|!=} "regular-expression"]
1854       [TIMEOUT number SECONDS]       [TIMEOUT number SECONDS] [[<X>] <Y> CYCLES]
1855       THEN action       THEN action
1856       [ELSE IF RECOVERED THEN action]       [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1857    
1858  Where URL-spec is an URL on the standard form as specified in RFC  Where URL-spec is an URL on the standard form as specified in RFC
1859  2396:  2396:
# Line 1849  is as follows (keywords are in capital a Line 1903  is as follows (keywords are in capital a
1903  [brackets]):  [brackets]):
1904    
1905    IF FAILED ICMP TYPE ECHO    IF FAILED ICMP TYPE ECHO
1906       [COUNT number] [WITH] [TIMEOUT number SECONDS]       [COUNT number] [WITH] [TIMEOUT number SECONDS] [[<X>] <Y> CYCLES]
1907       THEN action       THEN action
1908       [ELSE IF RECOVERED THEN action]       [ELSE IF RECOVERED [[<X>] <Y> CYCLES] THEN action]
1909    
1910  The rules for action and timeout are the same as those mentioned  The rules for action and timeout are the same as those mentioned
1911  above in the CONNECTION TESTING section. The count parameter  above in the CONNECTION TESTING section. The count parameter
# Line 2731  insensitive. Line 2785  insensitive.
2785                   monit's control otherwise the service isn't                   monit's control otherwise the service isn't
2786                   monitored.                   monitored.
2787   cpu             Must be followed by a compare operator, a number   cpu             Must be followed by a compare operator, a number
2788                   with "%", optionally a maximum number of cycles                   with "%" and an action. This statement is used
2789                   and an action. This statement is used to check                   to check the cpu usage in percent of a process
2790                   the cpu usage in percent of a process with its                   with its children over a number of cycles. If
2791                   children over a number of cycles.  If the                   the compare expression matches then the specified
                  compare expression matches then the specified  
2792                   action is executed.                   action is executed.
2793   mem             The equivalent to the cpu token for memory of a   mem             The equivalent to the cpu token for memory of a
2794                   process (w/o children!).  This token must be                   process (w/o children!).  This token must be
2795                   followed by a compare operator a number with                   followed by a compare operator a number with
2796                   unit {B|KB|MB|GB|%|byte|kilobyte|megabyte|                   unit {B|KB|MB|GB|%|byte|kilobyte|megabyte|
2797                   gigabyte|percent}, optionally a maximum number                   gigabyte|percent} and an action.
                  of cycles and an action.  
2798   loadavg         Must be followed by [1min,5min,15min] in (), a   loadavg         Must be followed by [1min,5min,15min] in (), a
2799                   compare operator, a number, optionally a maximum                   compare operator, a number and an action. This
2800                   number of cycles and an action.  This statement                   statement is used to check the system load average
2801                   is used to check the system load average over a                   over a number of cycles. If the compare expression
                  number of cycles. If the compare expression  
2802                   matches then the specified action is executed.                   matches then the specified action is executed.
2803   children        This is the number of child processes spawn by a   children        This is the number of child processes spawn by a
2804                   process. The syntax is the same as above.                   process. The syntax is the same as above.

Legend:
Removed from v.1.167  
changed lines
  Added in v.1.168

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