From owner-freebsd-hackers Sun Jan 28 06:18:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA07472 for hackers-outgoing; Sun, 28 Jan 1996 06:18:52 -0800 (PST) Received: from plato.algonet.se (mail.algonet.se [193.12.207.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA07461 for ; Sun, 28 Jan 1996 06:18:48 -0800 (PST) Received: from sophocles.algonet.se (mal@sophocles.algonet.se [193.12.207.10]) by plato.algonet.se (8.6.12/hdw.1.0) with ESMTP id PAA08765; Sun, 28 Jan 1996 15:18:33 +0100 Received: (from mal@localhost) by sophocles.algonet.se (8.6.12/hdw.1.0) id PAA04187; Sun, 28 Jan 1996 15:17:41 +0100 Date: Sun, 28 Jan 1996 15:17:41 +0100 Message-Id: <199601281417.PAA04187@sophocles.algonet.se> From: Mats Lofkvist To: imb@scgt.oz.au CC: nate@sri.MT.net, hackers@FreeBSD.org In-reply-to: <199601281401.BAA00989@asstdc.scgt.oz.au> (message from michael butler on Mon, 29 Jan 1996 01:01:19 +1100 (EST)) Subject: Re: ntp stuff? Sender: owner-hackers@FreeBSD.org Precedence: bulk > > (I also had to set TIMER_FREQ in my config file to make ntp not lose sync > > after a few minutes due to too large drifts.) > > I usually "tweak" it using something like .. > > tickadjflags="-Aq -t 9998" > > .. which renders a clock with this sort of characteristic .. I was told changing TIMER_FREQ was preferred because changing the tick would cause jumps in time. (I guessed this is because the time given between ticks is based on last tick + something using TIMER_FREQ. Correct?) _ Mats Lofkvist mal@algonet.se