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
Date: Mon, 7 Aug 2006 20:42:53 -0400 [thread overview]
Message-ID: <20060808004253.GA51122@kris.home> (raw)
In-Reply-To: <f157e88f8c3aa52a456e862741e34902@quanstro.net>
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.
next prev parent reply other threads:[~2006-08-08 0:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:12 erik quanstrom
2006-08-08 0:42 ` Kris Maglione [this message]
2006-08-08 1:39 ` erik quanstrom
2006-08-08 1:46 ` andrey mirtchovski
2006-08-08 2:37 ` erik quanstrom
2006-08-08 1:59 ` andrey mirtchovski
2006-08-08 3:10 ` erik quanstrom
2006-08-08 6:09 ` Steve Simon
2006-08-08 6:15 ` andrey mirtchovski
2006-08-08 6:21 ` andrey mirtchovski
2006-08-08 15:00 ` John Floren
2006-08-08 2:09 ` geoff
2006-08-08 3:40 ` erik quanstrom
2006-08-08 3:09 ` Kris Maglione
2006-08-08 14:53 ` Russ Cox
2006-08-08 20:07 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060808004253.GA51122@kris.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).