What IS the right NTP behaviour ?

[Erik Cederstrand]

> Den 23/09/2015 kl. 22.33 skrev dirkx at webweaving.org:
> 
> 
>> On 23 Sep 2015, at 21:27, Brian Reichert <reichert at numachi.com> wrote:
>> 
>> On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote:
>>> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle <tim at kientzle.com> wrote:
>>>> One concern I keep running into:  Using NTP in VMs that are frequently suspended/resumed.  Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew).
>>> 
>>> I would assume your hypervisor would sync the clock upon VM events. Does it not?
>> 
>> In my VMs that run an NTP client, I keep the hypervisor out of the
>> loop, and let the guest's NTP client to it's work.
> 
>> ..http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427
> 
> Aye - but I’ve not found any clean way of doing that — now a small rc.d file does a stop of ntpd, an ntpdate (because the jumps are bigger than what ntpd by default will accomodate) and a restart of ntpd.

Does "tinker panic 0" in /etc/ntp.conf not work for you?

Erik