Date: Mon, 30 Jun 2008 18:59:21 +0200 From: Bernd Walter <ticso@cicely7.cicely.de> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Bernd Walter <ticso@cicely7.cicely.de>, freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: RTC problem Message-ID: <20080630165919.GR17364@cicely7.cicely.de> In-Reply-To: <7576.1214841263@critter.freebsd.dk> References: <20080630151740.GQ17364@cicely7.cicely.de> <7576.1214841263@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 30, 2008 at 03:54:23PM +0000, Poul-Henning Kamp wrote: > In message <20080630151740.GQ17364@cicely7.cicely.de>, Bernd Walter writes: > > >But since ntpd only tunes the softclock and never sets the RTC it > >allows the RTC to run completely unsyncronized. > >Is there a way to regulary trigger a write to the RTC without > >disturbing ntpd, so that the offset never gets large? > > Ideally the adjkerntz we run in cron every night should do that. > > The easiest way would be to add a sysctl that when written does it, > thatway systems without adjkerntz could do it with a cronjob that > just sysctl's that variable directly. Ok - a sysctl which, when written calls resettodr(). Plus adding this call to adjkerntz independend of wall_cmos_clock existence. I wonder if people might forget about this when they remove adjkerntz from a small system. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080630165919.GR17364>