Hello LDM'ers,
I found a bug, fixed in LDM version 6.17.3 alpha, that won't be fixed even
if you install 6.13.17, whenever it is released, if the LDM is already on
your server.
The problem is in the etc/registry.xml file. Go into the file and locate
this line, which is currently installed in 6.13.16 and all versions
previous::
<servers>ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu otc1.psu.edu
timeserver.unidata.ucar.edu</servers>
When you start the LDM, it checks to make sure that your system clock is
accurate. If it is not, then it is supposed to flag you.
The problem is, these servers are defunct. This causes two things to happen:
1. A slow (or slower) starting time fo the LDM
2. The LDM is unable to check your system clock for accuracy
To fix this issue, replace the line above, with this:
<servers>pool.ntp.org</servers>
OR, if you are in the National Weather Service or a company and use an
internal server, use that AND, if the firewall allows, use pool.ntp.org as
a backup. By using the example of the original line, separate each time
server name with a space, withe the first one listed being local IF you
have one.
And if you install any future LDM version, the LDM installation will keep
your registry.xml file and changes you made to it, undisturbed.
So, does anybody really know what time it is? Does anybody really care? If
so, I can't imagine why. Because once you fix this, you've all got time
enough to cry.
Gilbert
--
----
Gilbert Sebenste
Consulting Meteorologist
AllisonHouse, LLC
