Changes between Version 4 and Version 5 of WatchDog


Ignore:
Timestamp:
Feb 11, 2008, 10:05:43 AM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WatchDog

    v4 v5  
    33[[T(DesignDocument)]]
    44
    5 A '''watchdog''' is a mechanism for detecting system states (e.g. full filesystems, database failures, etc.) that require immediate attention by project staff. Typically the desired response to such a condition is to notify a pager, sending a short text description.
     5A '''watchdog''' is a mechanism for detecting system states
     6(e.g. full filesystems, database failures, etc.)
     7that require immediate attention by project staff.
     8Typically the desired response to such a condition is to notify a pager,
     9sending a short text description.
    610
    711BOINC provides a framework for defining watchdogs:
    812
    9  * A set of '''watchdog scripts''' are run from cron. Each script checks for an error condition, and present, it appends a descriptive line to an error log file. An example is '''wd_nresults_changing.php''', which makes sure that the number of results changes.
    10  * The script '''wd.php''', also run from cron, scans the error log files. If any has been updated since the last run, it sends email to a set of recipients, containing the last line of the file.
     13 * A set of '''watchdog scripts''' are run as periodic tasks. Each script checks for an error condition, and present, it appends a descriptive line to an error log file. An example is '''wd_nresults_changing.php''', which makes sure that the number of results changes.
     14 * The script '''watchdogs.php''', also run as a periodic task, scans the error log file. If it has been updated since the last run, it sends email to a set of recipients, containing the last line of the file.
    1115
    12 These files are in the sched/ directory.
     16These files are in the html_ops/ directory.