From owner-freebsd-net@FreeBSD.ORG Tue Jul 7 15:54:07 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32C0B1065672 for ; Tue, 7 Jul 2009 15:54:07 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-14.arcor-online.net (mail-in-14.arcor-online.net [151.189.21.54]) by mx1.freebsd.org (Postfix) with ESMTP id B041C8FC13 for ; Tue, 7 Jul 2009 15:54:06 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-19-z2.arcor-online.net (mail-in-19-z2.arcor-online.net [151.189.8.36]) by mx.arcor.de (Postfix) with ESMTP id 47D4B28ADFD for ; Tue, 7 Jul 2009 17:54:05 +0200 (CEST) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mail-in-19-z2.arcor-online.net (Postfix) with ESMTP id 535146BFBD for ; Tue, 7 Jul 2009 17:54:05 +0200 (CEST) Received: from lorvorc.mips.inka.de (dslb-092-075-193-151.pools.arcor-ip.net [92.75.193.151]) by mail-in-09.arcor-online.net (Postfix) with ESMTPS id 073401AF793 for ; Tue, 7 Jul 2009 17:54:04 +0200 (CEST) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-09.arcor-online.net 073401AF793 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.3/8.14.3) with ESMTP id n67Fs4IJ077296 for ; Tue, 7 Jul 2009 17:54:04 +0200 (CEST) (envelope-from mailnull@lorvorc.mips.inka.de) Received: (from mailnull@localhost) by lorvorc.mips.inka.de (8.14.3/8.14.3/Submit) id n67Fs4jR077295 for freebsd-net@freebsd.org; Tue, 7 Jul 2009 17:54:04 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Tue, 7 Jul 2009 15:54:04 +0000 (UTC) Message-ID: References: <20090702084608.GA59311@roberto-al.eurocontrol.fr> <200907020955.aa73037@walton.maths.tcd.ie> <20090706233701.GA30824@ringworld.transsys.com> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-net@freebsd.org Subject: Re: NTP - default /etc/ntp.conf X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2009 15:54:07 -0000 Louis Mamakos wrote: > > Shouldn't ntpd have figured out by now that the clock is gone (I > > unplugged it yesterday) and have switched into orphan mode? > > It seems like orphan mode is something that you'd run on an ensemble > of local machines to ensure that they continue to be synchronized with > each other because that's deemed important for some application need. > I don't understand why you'd go to all this trouble on a single host > to simulate NTP clock synchronization when in fact the local clock > isn't synchronized to anything? This particular setup is a single server with a bunch of clients. Even if the server loses its reference clock, the clients should all continue to have the same time. If the server reports that it is unsynchronized, the clients will ignore it and drift apart. Now, in my test case the server keeps thinking that it is synchronized to a dead refclock, which is fine for the clients. But I still wonder why it didn't switch into orphan mode. -- Christian "naddy" Weisgerber naddy@mips.inka.de