From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] Keeping a Plan9 domain's time consistent
Date: Sat, 19 Dec 1998 07:55:57 +0200 [thread overview]
Message-ID: <19981219055557.Mbjt5_gJ2PKSHgJrkxH8-8GcmGhptIg1rvhawWULl2Q@z> (raw)
According to G. David Butler:
>
> I've started thinking about how to keep time consistent
> in a Plan9 system. This is one problem that is common
> with most distributed systems.
>
You bet! I keep having to rewind the clock on my file server because
it foolishly believes it is running on sensible hardware :-(
> We could use timed between the file servers and increase
> the frequency of the cpu/terminal systems syncing their
> time using the existing stat of /. This would keep the
> overhead of the timed protocol down.
>
I run a silly combination of NTP and timed amongst some six hosts, and
the result seem surprisingly good (this on NetBSD - the NT boxes aren't
yet synced, although SAMBA would take care of that, I believe). I'd
love to do better though, and the Plan 9 docs hint that it may be
possible, where they suggest that Bell Labs use an external source for
their time.
> Or we could run ntp on the auth server and slave all the
> other systems from that.
>
The NTP docs argue that timed and ntp should not run on the same host,
but I could find no good reason, nor a practical alternative. I'd love
this issue to be clarified.
++L
next reply other threads:[~1998-12-19 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-19 5:55 Lucio [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-12-23 8:36 Nigel
1998-12-19 12:21 Juhani
1998-12-18 20:34 Bengt
1998-12-18 17:28 G.David
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=19981219055557.Mbjt5_gJ2PKSHgJrkxH8-8GcmGhptIg1rvhawWULl2Q@z \
--to=9fans@9fans.net \
/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).