[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

splitting the CONDUIT feed

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: splitting the CONDUIT feed
  • Date: Fri, 15 Mar 2002 11:27:13 -0700
Hi Jim,

Here's how we split the CONDUIT feed.  First, we added this line to
/etc/hosts:

140.90.165.162  tgsv32.nws.noaa.gov     tgsv32 tgsv32_0 tgsv32_1
tgsv32_2 tgsv32_3 tgsv32_4

tgsv32.nws.noaa.gov is the host in Maryland from which we get the data. 
The following 6 names then becomes aliases for that host.

Then, in ldmd.conf we said:

request NMC2    ".*[09]$"       tgsv32_0
request NMC2    ".*[18]$"       tgsv32_1
request NMC2    ".*[27]$"       tgsv32_2
request NMC2    ".*[36]$"       tgsv32_3
request NMC2    ".*[45]$"       tgsv32_4

This "fools" the LDM into splitting the feed 5 ways.

As I said, there is a cost to this, which is the reason that we have not
publicized this more widely.  That is, instead of one rpc.ldmd on each
end of the connection, there are now five.  So, it has an impact beyond
the local host. In your case, this is all within your local network, so
you can do what you like.

Hope this helps.  Good luck with your RECLASS problem.  If you need more
help, the email address is support@unidata.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************