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

[LDM #EEM-529083]: proper config of ldmd.conf

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: [LDM #EEM-529083]: proper config of ldmd.conf
  • Date: Mon, 09 Jun 2014 11:11:14 -0600
Rodger,

> Thanks for your response. Our LDM runs on the same machine as the ingest of 
> the feed from our dish, so there's not a REQUEST entry in our ldmd.conf. Our 
> PDI NOAAPort system inserts products ingested by the dish into the LDM queue 
> using a PDI program. With this in mind, is it still possible to have an IDD 
> feed or two enabled through a REQUEST and not have any IDD feed actually 
> start up unless the feed from the dish stops or we start losing frames in 
> heavy rain or snow events. I don't want to be a burden on any of the IDD 
> sites that have allowed us to connect in a backup mode.

I think the cleanest way to do what you want would be to have an LDM on a 
second computer request from both your NOAAPORT ingest LDM and another IDD LDM. 
The overhead of the request to the IDD LDM would be negligible unless and until 
your NOAAPORT LDM went offline.

Do you have a second computer?

> Rodger

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EEM-529083
Department: Support LDM
Priority: Normal
Status: Closed