From owner-freebsd-stable@FreeBSD.ORG Tue Dec 19 12:52:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 314FB16A412 for ; Tue, 19 Dec 2006 12:52:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.200.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5103443CB7 for ; Tue, 19 Dec 2006 12:52:24 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc14) with ESMTP id <2006121912415101400445ahe>; Tue, 19 Dec 2006 12:41:51 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 81AC01FA037; Tue, 19 Dec 2006 04:41:51 -0800 (PST) Date: Tue, 19 Dec 2006 04:41:51 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20061219124151.GA33385@icarus.home.lan> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: ntpd flipping between PLL and FLL mode X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 12:52:29 -0000 This issue has been discussed in the past, although no one really concluded what the cause was, or if there were implications from it: http://www.mail-archive.com/freebsd-stable@freebsd.org/msg67325.html http://lists.freebsd.org/pipermail/freebsd-questions/2004-September/059279.html There's also a docs/ PR which may have implications in the sense that "something changed" between ntpd versions: http://lists.freebsd.org/pipermail/freebsd-doc/2006-October/011434.html There's an open bug report with the NTP folks about this: https://lists.ntp.isc.org/pipermail/bugs/2005-June/002174.html I can reproduce this behaviour on 3 different boxes with completely different hardware, all running 6.x. Below, in sequential order, are an AMD SMP box, a uni-proc Intel, and an Intel SMP box. Dec 19 00:22:26 icarus ntpd[624]: kernel time sync enabled 2001 Dec 19 01:47:48 icarus ntpd[624]: kernel time sync enabled 6001 Dec 19 02:04:52 icarus ntpd[624]: kernel time sync enabled 2001 Dec 19 01:51:07 eos ntpd[85369]: kernel time sync enabled 6001 Dec 19 02:08:10 eos ntpd[85369]: kernel time sync enabled 2001 Dec 19 03:33:34 eos ntpd[85369]: kernel time sync enabled 6001 Dec 18 18:29:38 medusa ntpd[99931]: kernel time sync enabled 2001 Dec 18 21:20:26 medusa ntpd[99931]: kernel time sync enabled 6001 Dec 18 21:37:32 medusa ntpd[99931]: kernel time sync enabled 2001 If this is completely normal behaviour, which many of the threads above state it is (although in a couple instances there's examples of the clock not being kept in sync while this is happening), then there's the issue of how to disable this kind-of logging. I looked at the ntpd code for this, and there does not appear to be a way to disable logging of this message without impacting other important ntpd messages. :-( So I guess my post here is to ask if anyone has extensive experience with this, and what the implications are. With ntpdate being phased out soon, most people will be expected to run ntpd, and therefore more support mails will be sent to the lists asking about this... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |