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

[IDD #TPV-537982]: conduit

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: [IDD #TPV-537982]: conduit
  • Date: Wed, 30 Sep 2009 11:40:12 -0600
Hi Matt,

re:
> when can we start pulling the feed?

Only Art can answer this one authoritatively.  In the
meantime, you can test to see if he has added the ALLOWs
for your machines:

<as 'ldm' on each of the machines you want to request CONDUIT>
notifyme -vl- -f CONDUIT -h ldm.meteo.psu.edu

'notifyme' will let you know if you are not ALLOWed to
request the data.  If you are, you should go ahead and
start ingesting using the 5-way split that we recommended
previously:

REQUEST CONDUIT "[09]$" ldm.meteo.psu.edu
REQUEST CONDUIT "[18]$" ldm.meteo.psu.edu
REQUEST CONDUIT "[27]$" ldm.meteo.psu.edu
REQUEST CONDUIT "[36]$" ldm.meteo.psu.edu
REQUEST CONDUIT "[45]$" ldm.meteo.psu.edu

By the way, it would be a good idea to setup your backup
machine to request the full set of CONDUIT from your
primary machine so that it can assume primary duty
as soon as possible after the primary becomes unavailable
for any reason.

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: TPV-537982
Department: Support IDD
Priority: Normal
Status: Closed