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

[IDD #DLB-942503]: 20170320: pavan.srcc.lsu.edu being replaces as LSU relay



Hi Yixin,

re:
> copied. Thank you.

OK, thanks.

I finished setting up the LDM on taku yesterday afternoon, configured
the LDM to have a 16 GB queue (as a first guess; IDD relays should
have sizable queues so that downstreams can go offline for awhile
and then come back and not miss data), modified the REQUEST lines
in the LDM configuration file, ~ldm/etc/ldmd.conf, to also REQUEST
the NOTHER feed from upstreams other than mistral (the REQUEST to
mistral is ANY, so the NOTHER data was already there), and started
it.

Real-time statistics from taku can be seen on our IDD real-time
status page:

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?taku.srcc.lsu.edu

(After looking at the real-time stats page)

OK, I see that you have modified the REQUESTs on taku to include
feeds that do not originate from NOAAPort:

CONDUIT
EXP
FNMOC
LIGHTNING
NEXRAD2

NB:

Please remember that you can NOT relay LIGHTNING data products to
downstreams outside of your campus!  This is VERY important as
providing such a relay could jeopardize the free access to 
LIGHTNING data that the Unidata university community enjoys!!

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: DLB-942503
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.