From owner-freebsd-current Sun Mar 26 19:45:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA02527 for current-outgoing; Sun, 26 Mar 1995 19:45:13 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA02520 for ; Sun, 26 Mar 1995 19:45:07 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id WAA23367 for current@freebsd.org; Sun, 26 Mar 1995 22:44:59 -0500 Received: by starkhome.cs.sunysb.edu (8.6.11/1.34) id WAA06229; Sun, 26 Mar 1995 22:44:17 -0500 Date: Sun, 26 Mar 1995 22:44:17 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503270344.WAA06229@starkhome.cs.sunysb.edu> To: current@FreeBSD.org Subject: Kernel time and xntpd Sender: current-owner@FreeBSD.org Precedence: bulk I have been running xntpd for awhile now on some of my FreeBSD systems, and it seems that xntpd has to perform a step adjustment of about -0.14 sec approximately once an hour to stay in sync with a non-FreeBSD remote time source. This is an error of about 40ppm. On the other hand, other FreeBSD systems seem to stay in sync with a FreeBSD master with a stability of less than 1ppm. This would seem to indicate that there are still errors in the kernel timekeeping in FreeBSD. Are any currently known? - Gene