From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] timesync doubletime
Date: Tue, 8 Aug 2006 07:53:49 -0700 [thread overview]
Message-ID: <ee9e417a0608080753t1756e7eeg58c9e52b85e78e83@mail.gmail.com> (raw)
In-Reply-To: <f157e88f8c3aa52a456e862741e34902@quanstro.net>
> the rtc clock in one of my machines runs a bit slow -- maybe 2 minutes a month.
> i ran timesync -h /srv/sources and now the system clock runs ~28 sec/min too fast.
> killing timesync had no effect.
Killing timesync probably did have an effect.
As Kris pointed out, if you were a few minutes behind sources
then maybe timesync was running time fast to catch up. Killing it
doesn't help -- now time will run fast forever, when if you'd left it,
it probably would have slowed to regular speed once it caught up.
The speed in use at time of kill is what the kernel will use until
told otherwise.
Also, you might get more precise results by using NTP instead
of relying on a long-distance TCP connection to sources.
Russ
next prev parent reply other threads:[~2006-08-08 14:53 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
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 [this message]
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=ee9e417a0608080753t1756e7eeg58c9e52b85e78e83@mail.gmail.com \
--to=rsc@swtch.com \
--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).