Date: Tue, 7 Jul 2009 15:54:04 +0000 (UTC) From: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-net@freebsd.org Subject: Re: NTP - default /etc/ntp.conf Message-ID: <h2vr2s$2bf6$1@lorvorc.mips.inka.de> References: <20090702084608.GA59311@roberto-al.eurocontrol.fr> <200907020955.aa73037@walton.maths.tcd.ie> <h2t1pr$28me$1@lorvorc.mips.inka.de> <20090706233701.GA30824@ringworld.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Louis Mamakos <louie@transsys.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h2vr2s$2bf6$1>