Date: Mon, 30 Jun 2008 17:51:38 +0200 From: Aragon Gouveia <aragon@phat.za.net> To: ticso@cicely.de Cc: freebsd-current@freebsd.org Subject: Re: RTC problem Message-ID: <20080630155138.GA3084@phat.za.net> In-Reply-To: <20080630151740.GQ17364@cicely7.cicely.de> References: <20080630151740.GQ17364@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
adjkerntz(8) ? | By Bernd Walter <ticso@cicely7.cicely.de> | [ 2008-06-30 17:30 +0200 ] > This is not about a specific hardware - I have a general problem. > Normaly I run ntpdate and ntpd - ntpdate sets the time on boot and > then ntpd takes over to keep it in sync. > What recently happend was that a server with a multiple years uptime > rebootet because of a power failure and the local ntp-server wasn't > up early enough, so ntpdate didn't set the clock. > ntpd didn't tune the clock either, because the offset was too big. > I know from debugging RTC support on arm, that the RTC only gets > written on explizit time setting with ntpdate, date and such. > 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? > Of course I can configure ntpd to accept a large offset, but it seems > wrong to me that the RTC runs unsyncronized for a large time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080630155138.GA3084>