Date: Thu, 16 Jul 1998 09:39:46 -0400 (EDT) From: Brian Feldman <green@zone.baldcom.net> To: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <Pine.BSF.3.96.980716093629.28008A-100000@zone.baldcom.net> In-Reply-To: <2148.900592940@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jul 1998, Poul-Henning Kamp wrote: > In message <35adf2b5.224800464@mail.cetlink.net>, John Kelly writes: > > >>>Argh! So should I change both kern.timecounter.frequency and the > >>>machine dependent variable? Will that work? > >> > >>This is why it is so much easier just to start xntpd and be done with it. > >> > >>They only time where you need to tweak any sysctl's is when the hardware > >>is outside the capture range (+/- 128 PPM ?) of xntpd. > > > >That's true for my hardware. > > > >>After I implemented timecounters, time keeping doesn't depend on tick, > >>and since the adjustment is for all practical purposes continuous, > >>there is no benefit of tweaking the sysctls. > > > >That sounds contradictory to the previous paragraph. So why tweak > >sysctls when it's outside the capture range of xntpd? > > To get it inside xntpd's capture range ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > FWIW, I've always just been band-aiding the problem, i.e. add "ntpdate tick.usno.navy.mil" to ppp.linkup, or if having a real connection, sticking it in crontab. Brian Feldman green@zona.baldcom.net 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?Pine.BSF.3.96.980716093629.28008A-100000>