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

[LDM #TMK-479992]: Monotonic clock confusion

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 #TMK-479992]: Monotonic clock confusion
  • Date: Fri, 29 Aug 2008 07:16:55 -0600
Hi Mike,

re:
> We plan to install LDM 6.6.5 on a virtual machine running Linux.

I have done this as a proof of concept on my Windows XP laptop using the Fedora 
8,9 and Ubuntu
distributions of Linux.  A couple/few months back a Unidata user in Florida 
reported using
the same sort of setup on a machine that he is using "operationally".

> The installation instructions say  that the host machine should have a 
> monotonic clock
> accurate to within 1 ms. To achieve this, the instructions suggest using ntpd

An accurate clock is needed most when connections break and are reestablished.  
While a
connection is active, the accuracy of the clock is of secondary importance.  
The reason
for the need for clock accuracy is so a connection will not miss products 
during a 
(re)connect process.


>-- which seems like a contradiction because ntpd itself sets the clock back.

ntpd will adjust the clock.  This can be either setting the clock back or 
forward.

> In addition, our VM software has known issues with system time that are 
> addressed using
> other tools that periodically alter the time in the same manner as ntpd.

In my proof-of-concept testing, I used ntpdate.

> Will these tools interfere with LDM?

No.  A number of Unidata sites still use ntpdate run out of cron to set their 
clocks.
Again, this is not a problem as long as a feed stays connected.  It can be 
problematic
if the connection breaks and is reestablished often.

> We would be grateful if you could please clarify this matter for us and pass 
> on any
> advice you might have regarding how we should proceed.

The best thing to do is to try the clock setting procedure recommended by your 
VM
and see if it suits your needs.
 

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: TMK-479992
Department: Support LDM
Priority: Normal
Status: Closed