From owner-freebsd-hackers@freebsd.org Wed Sep 23 20:35:11 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F71BA074B7 for ; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 03EB91E2E for ; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 000DBA074B6; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3C33A074B5 for ; Wed, 23 Sep 2015 20:35:10 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A57A1E2D for ; Wed, 23 Sep 2015 20:35:09 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from [192.168.1.21] (s55978988.adsl.online.nl [85.151.137.136]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id t8NKXjLm052927 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Sep 2015 22:33:47 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host s55978988.adsl.online.nl [85.151.137.136] claimed to be [192.168.1.21] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: What IS the right NTP behaviour ? From: dirkx@webweaving.org In-Reply-To: <20150923192729.GB78209@numachi.com> Date: Wed, 23 Sep 2015 22:33:45 +0200 Cc: Brandon Vincent , hackers@freebsd.org, Poul-Henning Kamp Content-Transfer-Encoding: quoted-printable Message-Id: References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> To: Brian Reichert X-Mailer: Apple Mail (2.2104) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Wed, 23 Sep 2015 22:33:47 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:35:11 -0000 > On 23 Sep 2015, at 21:27, Brian Reichert wrote: >=20 > On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: >> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = 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). >>=20 >> I would assume your hypervisor would sync the clock upon VM events. = Does it not? >=20 > 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=3Den_US&c= md=3DdisplayKC&externalId=3D1006427 Aye - but I=E2=80=99ve not found any clean way of doing that =E2=80=94 = 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. You=E2=80=99d perhaps want the kernel or userland (ntpd) to understand = more of this. Dw.