From: Bengt Kleberg bengt.kleberg@swip.net
Subject: [9fans] Keeping a Plan9 domain's time consistent
Date: Fri, 18 Dec 1998 21:34:08 +0100 [thread overview]
Message-ID: <19981218203408.Ew-qJx8UGrMmdfMD98Z_Lu5-2JJlBHizcC5_NXp9W4A@z> (raw)
In article <199812181728.LAA22026@ns.dbSystems.com>, 9fans@cse.psu.edu wrote:
> 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.
My favorite books on the subject (distributed systems) always suggest that
one should avoid a centralised solution. This is due to the lack of
scalability of such a solution. However, with a Plan9 system the auth
server is a centralised already, no?
> 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 will try to understand this and perhaps comment if I manage)
> Or we could run ntp on the auth server and slave all the
> other systems from that.
How about mount:ing /dev/time from the auth server? Would that save the
other systems from running ntp?
> 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?
>
Would a DNS like system make sense? File servers sync with the auth
server. Cpu servers sync with a file server (the least recently used).
Terminals sync with cpu servers (also the least recently used). I hope
this is a none centralised suggestion, and that it might scale.
next reply other threads:[~1998-12-18 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-18 20:34 Bengt [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-19 5:55 Lucio
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=19981218203408.Ew-qJx8UGrMmdfMD98Z_Lu5-2JJlBHizcC5_NXp9W4A@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).