From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Keeping a Plan9 domain's time consistent
Date: Fri, 18 Dec 1998 11:28:09 -0600 [thread overview]
Message-ID: <19981218172809.a0Bl0oWjCkHPdC3ljSXFzrMxlbnujky0ASLDFp1gzzI@z> (raw)
Hello 9fans!
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.
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.
Or we could run ntp on the auth server and slave all the
other systems from that.
The only requirement is that the protocol be il or udp
based so we don't have to add tcp to the file servers.
Any thoughts?
David Butler
gdb@dbSystems.com
next reply other threads:[~1998-12-18 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-18 17:28 G.David [this message]
1998-12-18 20:34 Bengt
1998-12-19 5:55 Lucio
1998-12-19 12:21 Juhani
1998-12-23 8:36 Nigel
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=19981218172809.a0Bl0oWjCkHPdC3ljSXFzrMxlbnujky0ASLDFp1gzzI@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).