From owner-freebsd-current Tue Jul 14 19:39:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29393 for freebsd-current-outgoing; Tue, 14 Jul 1998 19:39:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29388 for ; Tue, 14 Jul 1998 19:39:40 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id WAA10207 for ; Tue, 14 Jul 1998 22:39:33 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: current@FreeBSD.ORG Subject: tickadj -t not changing tick Date: Wed, 15 Jul 1998 02:42:09 GMT Message-ID: <35ac1492.102379029@mail.cetlink.net> References: <199807150208.WAA29904@xxx.video-collage.com> In-Reply-To: <199807150208.WAA29904@xxx.video-collage.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA29389 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone else noticed that tickadj -t is broken in -current? It does not change the tick. I can tell by setting the tick to a very low or high value like 9951 or 10049, and then running ntpdate -b every few minutes to see if the time step function of ntpdate is compensating for the low/high tick value. In 2.2.5 it does, but in -current it does not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message