Changeset 684 in ntrip for trunk/BNC/bnchelp.html


Ignore:
Timestamp:
Feb 13, 2008, 9:27:06 PM (17 years ago)
Author:
weber
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r683 r684  
    7979&nbsp; &nbsp; &nbsp; 3.7.2. <a href=#syncwait>Wait for Full Epoch</a><br>
    8080&nbsp; &nbsp; &nbsp; 3.7.3. <a href=#syncfile>Output File</a><br>
    81 3.8. <a href=#advnote>Advisory Notice</a><br>
     813.8. <a href=#advnote>Advisory Note</a><br>
    8282&nbsp; &nbsp; &nbsp; 3.8.1. <a href=#advsegm>Inspect Segment</a><br>
    8383&nbsp; &nbsp; &nbsp; 3.8.2. <a href=#advfail>Failure Threshold</a><br>
    … …  
    372372</p>
    373373
    374 <p><a name="advnote"><h4>3.8. Advisory Notice</h4></p>
     374<p><a name="advnote"><h4>3.8. Advisory Note</h4></p>
    375375
    376376<p>
    … …  
    409409</p>
    410410<p>
    411 All the events are reported in the Log file/section. They can also be passed on as parameters to a shell script or batch file to generate an advisory notice to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
     411All the events are reported in the Log file/section. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
    412412</p>
    413413
    414414<p><a name="advscript"><h4>3.8.4 Advisory Script - optional </h4></p>
    415415<p>
    416 As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory notice to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (\%1 and \%2 on Windows systems or \$1 and \$2 on UNIX/Linuxsystems).
     416As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory note to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (\%1 and \%2 on Windows systems or \$1 and \$2 on UNIX/Linuxsystems).
    417417</p>
    418418<p>
    … …  
    426426sleep $((60*RANDOM/32767))
    427427cat | mail -s "BNC: $2 Stream $1" email@address &lt;&lt;!
    428 Advisory Notice to BNC User,
     428Advisory Note to BNC User,
    429429Please note a $2 advisory from BNC for stream $1 dated `date`.
    430430Regards, BNC
    … …  
    542542<li>
    543543The source code provided by NRCan for decoding RTIGS streams is 32-bit dependent. Hence the BNC executable generated for 64-bit Linux systems would only run when compiled using the -m32 compiler option.
     544</li>
     545<li>
     546Once BNC has been started, its configuration can not be changed as long as it is stopped. A reconfiguration on-the-fly is not implemented.
    544547</li>
    545548<br>
Note: See TracChangeset for help on using the changeset viewer.