Showing entries tagged [ldm]

LDM 6.11.7 Released

Version 6.11.7 of the LDM has been released. It fixes a bug that caused the NOAAPORT ingest component to crash.

Here's the story:

The NOAAPORT Satellite Broadcast System contains a lot of GRIB-2 messages. Such messages require external tables in order to be interpreted. The NOAAPORT ingest component of the LDM uses the tables that come with GEMPAK to interpret GRIB-2 messages in order to generate meaningful LDM product-identifiers. Unfortunately, not all tables are complete and creators of GRIB-2 messages are free to add data for which no corresponding table-entry exists.

[Read More]

LDM 6.11.6 Released

Version 6.11.6 of the LDM has been released. Continuing the trend of version 6.11.5, this version doesn't have the PNG or ZLIB packages bundled-in -- and for the same reasons: bundling is no longer necessary, security is enhanced by removing them, and the size of the LDM package is reduced. You must have the PNG and ZLIB development packages installed in order to build this version of the LDM.

[Read More]

LDM 6.11.5 Released

Version 6.11.5 of the LDM has been released. This version doesn't have the "libxml2" package bundled-in; consequently, the "libxml2" development package must be installed on the host system before the LDM package can be built. The development package is necessary because the runtime package doesn't have the required header-files (development packages usually have the word "devel" in their name). If you're using version 6.11.4 of the LDM, have not encountered any problems with it, and don't care which "libxml2" package the LDM uses, then there's no need to upgrade to LDM 6.11.5.

[Read More]

LDM 6.11.4 Released

Version 6.11.4 of the Local Data Manager (LDM) has been released. This version fixes and improves the defense against a denial-of-service attack, which is new with version 6.11. Getting the defense right was trickier than initially thought.

[Read More]

LDM 6.11.2 Released

Version 6.11.2 of the LDM has been released.

This version modifies the rejection of a subscription by a downstream LDM. Before, both FEEDME subscriptions and NOTIFYME subscriptions were treated identically: if a downstream site had a REQUEST entry for feedtype ANY and pattern ".*", then a subsequent, default notifyme(1) execution would be rejected by the upstream LDM because it duplicated the REQUEST-based subscription. Now, the upstream LDM will not reject the notifyme(1)-based subscription because the two subscription categories are handled separately.

This version can be downloaded at https://www.unidata.ucar.edu/downloads/ldm.

This version's homepage.

News@Unidata
News and information from the Unidata Program Center
News@Unidata
News and information from the Unidata Program Center

Welcome

FAQs

Developers’ blog

Take a poll!

What if we had an ongoing user poll in here?

Browse By Topic
Browse by Topic
« July 2024
SunMonTueWedThuFriSat
 
3
4
5
6
7
8
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
   
       
Today