Tom, > It is using ntpd and ntpdate is only used just before ntpd is started. > What is really funny is that it would also happen with ntpd NOT > running. Vmware has an option to fix the time in its vms but as best I > can tell it is definitely disabled in this case. This "app note" > > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006086 > touches on about what is happening. According to the note, you must be running a version of Linux that's at least 3 years old. If you upgrade to a more modern version, does the problem dissapear? > It just so happens we're using a > kernel that you can dynamically change the effective HZ (divider= kernel > option) and when it is set to effective HZ=100, the problem is worse - > maybe since the possible back steps are larger. > > Tom Regards, Steve Emmerson Ticket Details =================== Ticket ID: WCE-307093 Department: Support LDM Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.