User Tools

Site Tools


operations:documentation.logmonitor_eremotectrl

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
operations:documentation.logmonitor_eremotectrl [2016/05/19 03:56]
Tiege McCarthy [Starting the log monitor]
operations:documentation.logmonitor_eremotectrl [2016/05/19 03:57]
Tiege McCarthy [Starting the log monitor]
Line 25: Line 25:
     - Once a setup is complete there may be several hours before the next log entry at the experiment start. In this case, a series of incessant beeps after 15 minutes could get annoying. Pressing the "Reset watchdog"​ button will reset the log line counter to zero, meaning that the time difference will not be checked again until there'​s a new entry.     - Once a setup is complete there may be several hours before the next log entry at the experiment start. In this case, a series of incessant beeps after 15 minutes could get annoying. Pressing the "Reset watchdog"​ button will reset the log line counter to zero, meaning that the time difference will not be checked again until there'​s a new entry.
  
-Too set the optimal timeout values in the log monitor open a terminal on ops2 and type ./​watchdog_check.sh <​experiment name>, this will return a value to input into the log monitor for each telescope involved in the experiment. ​+To set the optimal timeout values in the log monitor open a terminal on ops2 and type ./​watchdog_check.sh <​experiment name>, this will return a value to input into the log monitor for each telescope involved in the experiment. ​
 For example: For example:
 <​code>​ <​code>​
/home/www/auscope/opswiki/data/pages/operations/documentation.logmonitor_eremotectrl.txt · Last modified: 2016/12/20 04:05 by Jim Lovell