User Tools
operations:documentation.logmonitor_v3
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
operations:documentation.logmonitor_v3 [2016/12/20 04:20] Jim Lovell created |
operations:documentation.logmonitor_v3 [2017/08/16 10:35] (current) Jesse Swan |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| The new version of the log monitor works as a GUI and as a text-based interface, allowing you to monitor a telescope from a terminal window. It also now keeps a text log of its output, will take the telescope name and input log on the command line and has a few other bug fixes. | The new version of the log monitor works as a GUI and as a text-based interface, allowing you to monitor a telescope from a terminal window. It also now keeps a text log of its output, will take the telescope name and input log on the command line and has a few other bug fixes. | ||
| - | The first step is to make sure eRemoteCtrl is recording a log, or that you've started Dave's steam_log script. If you want to use the eRemoteCtrl log but don't know it's name, try <code>ls -lrt /vlbobs/ivs/logs | tail -20</code> and look for a likely named file. | + | The first step is to make sure eRemoteCtrl is recording a log, or that you've started Dave's stream_log script. If you want to use the eRemoteCtrl log but don't know it's name, try <code>ls -lrt /vlbobs/ivs/logs | tail -20</code> and look for a likely named file. |
| - | Usage:<code>pcfs_log_monitor_test.pl [-a <antenna ID [Hb|Ho|Ke|Yg|Ht]>] [-n (no GUI)] [-f <log file name>]</code> | + | Usage:<code>pcfs_log_monitor_test.pl [-a <antenna ID [Hb|Ho|Ke|Yg|Ht]>] [-n (no GUI)] [-f <log file name>] [-p <path to file (default /vlbobs/ivs/logs/)>] |
| + | </code> | ||
| * Specifying ''-n'' will start it in the text-based mode | * Specifying ''-n'' will start it in the text-based mode | ||
| - | * The log file name can be specified with a full path but if you just give the file name, the program will look for it in ''/vlbobs/ivs/logs'' | + | * Note: this was causing a bug where any file path specified other than ''/vlbobs/ivs/log/'' would result in an error message and program exit. Since I wanted to run this on (e.g.,) ''/tmp/ke.log'' I modified the script to allow an optional argument for the path ''-p'' which defaults to ''/vlbobs/ivs/log/''. |
| + | * usage would now be for a file in ''/vlbobs/ivs/logs/'' <code>pcfs_log_monitor_test.pl -n -a ke -f r1234ke_erc.log</code> as before, but for a file in (e.g.,) ''/tmp/'' <code>pcfs_log_monitor_test.pl -n -a ke -f ke.log -p /tmp/</code> | ||
| + | * The log file name can be specified with a full path but if you just give the file name, the program will look for it in ''/vlbobs/ivs/logs/'' | ||
| For example: | For example: | ||
/home/www/auscope/opswiki/data/attic/operations/documentation.logmonitor_v3.1482207650.txt.gz · Last modified: 2016/12/20 04:20 by Jim Lovell
Page Tools
