From owner-freebsd-hackers Sun Sep 7 23:33:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA11774 for hackers-outgoing; Sun, 7 Sep 1997 23:33:05 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA11769 for ; Sun, 7 Sep 1997 23:33:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00721; Mon, 8 Sep 1997 08:33:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA16081; Mon, 8 Sep 1997 08:10:10 +0200 (MET DST) Message-ID: <19970908081010.DS04250@uriah.heep.sax.de> Date: Mon, 8 Sep 1997 08:10:10 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: ywliu1@tao.sinanet.com.tw (Hoffmann Yen-Wei Liu) Subject: Re: Kernel clock runs inaccurately References: <199709080124.JAA14004@tao.sinanet.com.tw> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709080124.JAA14004@tao.sinanet.com.tw>; from Hoffmann Yen-Wei Liu on Sep 8, 1997 09:24:11 +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Hoffmann Yen-Wei Liu wrote: > I just got myself a new AMD k6-200, and I found out a major problem : > it runs about 30 seconds faster per day. So two days later, it runs > 2 minutes faster. However, the CMOS clock runs around 2 seconds slower > per day. This is acceptable to me. The master clock on my machine at work is much worse. I was contemplating to hack xntpd so it could use the RTC (CMOS) clock as a refclock, but unfortunately, didn't get very far. Mainly, i don't grok the xnptd refclock implementations, and how to add a new one. An alternative solution would be to hack a small userland daemon that wakes up every hour, reads the RTC, and calls adjtime(2) to compensate for the drift. I didn't want to do it this way because it's more of a hack than the xntpd solution would be, but i might go this route. All the people i've been asking for help with xntpd haven't been any help for me, they only attempted to explain me that i don't wanna do what i do want. (They are probably living in somewhat of an ivory tower with good NTP refclocks readily available on a cheap Internet, something that is not my situation, sitting behind dialup lines everywhere.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)