From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon,  7 Aug 2006 20:42:53 -0400
From: Kris Maglione <bsdaemon@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] timesync doubletime
Message-ID: <20060808004253.GA51122@kris.home>
References: <f157e88f8c3aa52a456e862741e34902@quanstro.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <f157e88f8c3aa52a456e862741e34902@quanstro.net>
User-Agent: Mutt/1.5.11
Topicbox-Message-UUID: 99189ac0-ead1-11e9-9d60-3106f5b1d025

On Mon, Aug 07, 2006 at 07:12:41PM -0500, erik quanstrom wrote:
>; cat /dev/rtc > /dev/time ; sleep 60 ; date ; date `{cat /dev/rtc}
>Mon Aug  7 19:07:11 CDT 2006
>Mon Aug  7 19:06:44 CDT 2006
>; ; cat /dev/rtc > /dev/time ; sleep 60 ; date ; date `{cat /dev/rtc}
>Mon Aug  7 19:09:34 CDT 2006
>Mon Aug  7 19:09:06 CDT 2006
>; ; ; cat /dev/rtc > /dev/time ; sleep 60 ; date ; date `{cat /dev/rtc}
>Mon Aug  7 19:10:19 CDT 2006
>Mon Aug  7 19:09:51 CDT 2006

That output isn't very useful. This would be more useful:
fn dates { date; date `{cat /dev/rtc} }
dates; cat /dev/rtc>/dev/time; dates; sleep 60; dates; sleep 60; dates

I suspect that the issue is that your clock is being synchronized to an ntp 
server which has a different time from your real time clock.

-- 
Kris Maglione

If it would be cheaper to buy a new unit, the company
will insist upon repairing the old one.