LDM 6.3.0 Release Notes
Changes from LDM 6.2.1
-
Added "-I ip_addr" option to LDM server. This
allows the user to specify what network interface
the server should use and enables 1) construction of director/server
clusters; and 2) running two, completely separate LDM systems
(under different users) on the same host simultaneously.
-
Added $ip_addr variable to ldmadmin(1)
configuration-file, ldmadmin-pl.conf, and modified
ldmadmin(1) accordingly.
-
Added "--enable-logging=localn" option to
configure(1) script to support the use of a
different logging facility and permit the running
of two LDM-s simultaneously.
-
Removed sending of final statistics from
rtstats(1)'s cleanup handler to avoid hanging the
program if the remote host is unavailable.
-
Added printing of IP address to "ldmadmin config"
command.
-
Removed "pqbinstats" directory from distribution
and eliminated "ldmadmin dostats" command.
-
Added "-P port" option to pqing(1) manual-page.
-
Added "ulogger" to GARBAGE macro in ulog/Makefile
so that the program will be removed by a "make
clean" or "make distclean".
-
Corrected misspelling in ldmadmin-pl.conf.
Known Problems
There's a potential bug in the upstream LDM code that could be activated if
and when
the upstream LDM hasn't sent a data-product for 30 seconds and a
subsequent attempt to flush the connection to the downstream LDM via a
NULLPROC message fails due to an RPC timeout. Whether or not this
results in incorrect behavior of the upstream LDM
depends on how the operating-system implements the TCP and socket layers.
On an AIX 5.2 system, at least, it can cause the upstream LDM to
hang -- resulting in the downstream LDM not receiving any data-products.
The solution is to upgrade the LDM on the upstream host to a later version.
Reporting Problems
If you encounter bugs or problems, please contact support@unidata.ucar.edu.
Include in the email all relevant items mentioned in the instructions.
