Date: Thu, 16 Jul 1998 10:47:06 -0400 (EDT) From: Mikhail Teterin <mi@aldan.algebra.com> To: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <199807161447.KAA06046@rtfm.ziplink.net> In-Reply-To: <35aeb750.209593961@mail.cetlink.net> from "John Kelly" at "Jul 16, 98 08:38:25 am"
next in thread | previous in thread | raw e-mail | index | archive | help
John Kelly once stated: =On Thu, 16 Jul 1998 09:23:27 +0200, Poul-Henning Kamp =<phk@critter.freebsd.dk> 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? There is no way this nonsense is going to be required for longer then a week, until one wizard or another commits a patch? My machine hare not only ran windoze without time problems before it came to my hands, it also ran FreeBSD-2.2 with clock running just peachy. -mi 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?199807161447.KAA06046>