From owner-freebsd-current@FreeBSD.ORG  Mon Jun 30 16:09:14 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0BE801065675
	for <freebsd-current@freebsd.org>; Mon, 30 Jun 2008 16:09:14 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: from mail.geek.sh (decoder.geek.sh [196.36.198.81])
	by mx1.freebsd.org (Postfix) with ESMTP id A44E88FC0A
	for <freebsd-current@freebsd.org>; Mon, 30 Jun 2008 16:09:13 +0000 (UTC)
	(envelope-from aragon@phat.za.net)
Received: by mail.geek.sh (Postfix, from userid 1000)
	id 9FF6224D22; Mon, 30 Jun 2008 17:51:38 +0200 (SAST)
Date: Mon, 30 Jun 2008 17:51:38 +0200
From: Aragon Gouveia <aragon@phat.za.net>
To: ticso@cicely.de
Message-ID: <20080630155138.GA3084@phat.za.net>
References: <20080630151740.GQ17364@cicely7.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080630151740.GQ17364@cicely7.cicely.de>
User-Agent: Mutt/1.4i
X-Operating-System: FreeBSD 4.10-RELEASE-p2 i386
Cc: freebsd-current@freebsd.org
Subject: Re: RTC problem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2008 16:09:14 -0000

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.