Showing entries tagged [ldm]

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.

LDM 6.11.1

Version 6.11.1 of the LDM package has been released.

This version improves the quality and reduces the quantity of messages logged by the new upstream LDM database feature introduced in LDM 6.11.0 and fixes an obscure bug in the pqing(1) utility.

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

This version's homepage.

LDM 6.11.0

Version 6.11.0 of the LDM package has been released.

The main new feature of this minor release is the addition of a transitory database of information on local upstream LDM processes. The database is transitory because it only exists while an LDM server is running. The database is primarily used to determine whether or not an incoming data-request duplicates or otherwise overlaps with an existing data-request from the same downstream host. If it does, then the request will be rejected.

[Read More]
News@Unidata
News and information from the Unidata Program Center
News@Unidata
News and information from the Unidata Program Center

Welcome

FAQs

Developers’ blog

Recent Entries:
Take a poll!

What if we had an ongoing user poll in here?

Browse By Topic
Browse by Topic
« March 2024
SunMonTueWedThuFriSat
     
2
3
5
7
8
9
10
11
12
13
14
15
16
17
18
19
21
22
23
24
26
27
28
29
30
31
      
Today