Date: Thu, 16 Jul 1998 16:13:26 GMT From: jak@cetlink.net (John Kelly) To: Mikhail Teterin <mi@aldan.algebra.com> Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <35ae253a.237736064@mail.cetlink.net> In-Reply-To: <199807161447.KAA06046@rtfm.ziplink.net> References: <199807161447.KAA06046@rtfm.ziplink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jul 1998 10:47:06 -0400 (EDT), Mikhail Teterin <mi@aldan.algebra.com> wrote: >=>The real way is to run ntpd, if you don't have a permanent connection, >=>consider looking into "burstmode" in the new xntpd4... > >=According to John Polstra in an archived message about tickadj, his >="real way" is to adjust the undisciplined clock before running xntpd, >=formerly with tickadj, but now via sysctl as Bruce suggested. I like >=the idea of getting the kernel synchronized with the hardware before >=trying to run xntpd. >[...] > >You, people, are just kidding, right? Totally and deadly serious. >There is no way this nonsense is going to be required for longer then >a week, until one wizard or another commits a patch? Many wizards have committed many patches just to get us where we are today. >My machine hare not only ran windoze without time problems before it >came to my hands That speaks for itself. >it also ran FreeBSD-2.2 with clock running just peachy. Clock? You mean a little X app? Wheeeee! (Sorry, but one silly post deserves another) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35ae253a.237736064>