Date: Tue, 9 Sep 1997 22:48:11 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Kernel clock runs inaccurately Message-ID: <19970909224811.AW46227@uriah.heep.sax.de> In-Reply-To: <19970908233231.09396@keltia.freenix.fr>; from Ollivier Robert on Sep 8, 1997 23:32:31 %2B0200 References: <199709080124.JAA14004@tao.sinanet.com.tw> <19970908081010.DS04250@uriah.heep.sax.de> <19970908233231.09396@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
As Ollivier Robert wrote: > > 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. > > It is already supported (if I understand what you want): > > peer 127.127.1.0 No, that's a pseudo-synchronization to the system clock. I was speaking about an actual synchronization to the RTC (CMOS clock). If you follow the thread backwards to its origin, you'll know why this can sometimes be a big difference. (Well, i've finally installed our DCF-77 clock today, so perhaps i've now got a real refclock instead, which takes the pressure for the RTC-hack from me for the machine i was intending this. Let's see how this cheap DCF-77 clock will do.) -- 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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970909224811.AW46227>