This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
operations:documentation.logmonitor_v3 [2017/08/16 10:34] Jesse Swan |
operations:documentation.logmonitor_v3 [2017/08/16 10:35] Jesse Swan |
||
---|---|---|---|
Line 8: | Line 8: | ||
* Specifying ''-n'' will start it in the text-based mode | * Specifying ''-n'' will start it in the text-based mode | ||
- | * 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/`. | + | * 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> | * 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'' | * 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'' |