Both data streams must have readers in order for data to flow out of either of them. If you are only interested in one of the data streams, run the /bin/cat output of the other FIFO into /dev/null . However, only one client may connect to each port. If there are more than one, the data will be garbeled.
If the client for the data streams is on another system, the FIFO outputs can be read by connecting to TCP/IP sockets 1501 and 1502 on the ingest machine. This channels the cat output from the FIFO into the socket. If the port numbers 1501, 1502 are not appropriate for your needs, they may be changed by editing /etc/services on the ingest machine.
Most of the actual work is done by the decoders, which are the client of the ingestor's data streams. Those things which are configurable are:
This file is used to mark WMO headers or classes of headers which are identified as ascii, but are actually all or partly binary data. Inclusion of the product ID in this file causes the product to flow on the binary data stream. If the file /opt/nport/exceptions
is missing or of zero length, no products will be redirected. When your system is delivered, the file will contain a product list suitable for the McIDAS XCD ingest package. If the file is modified, the changes take place immediately. You do not have to reboot the system. Comments on the structure of
/opt/nport/exceptions
reside in the companion file, /opt/nport/exceptions.doc
.
The startup script starts the ingestor automatically when the system is rebooted. It must use sh semantics, not ksh . In particular, two environmental variables are of interest to you, WRAP , and LOG . WRAP is the maximum number of megabytes of unread data the ingestor can store before overwriting occurs. At delivery, it is set to 100 (100 megabytes), which represents about 8.3 minutes of data. If the client decoder falls behind the ingestor by more than 8.3 minutes, the oldest data in the FIFOs is overwritten.
If the variable LOG is defined, then any console messages are also appended to a file whose name is in the LOG variable. The system is delivered with no log. If one is added, you must truncate or rotate it periodically, or it will grow forever. If a log is added, you must reboot in order for it to take effect. It is probably not a good idea to have a LOG . It could become very large if things are not working well.