Hemmann, Volker Armin posted
below, on Sat, 11 Feb 2006 23:56:59 +0100:
> today ntpd is the server daemon, for syncronizing several machines of a
> network, ntp-client the part, that sets your clock.
> please run ntp-client and forget ntpd.
That's not exactly correct. Correct that ntpd is a server that /can/
serve to sync a number of machines, but in so doing, it keeps /far/ better
time than simply stepping the clock with ntp-client will do. ntp-client
is a single-shot deal that syncs your time with whatever server you are
syncing to every time you run it -- that's it. ntpd will, once it knows
how your computer behaves time-wise, be able to keep your computer much
more accurate than it'd be on its own, even without a net connection or
external time source to syncronize with -- and much more accurately than
ntp-client can do as well, because ntp-client is doing jerky adjustments
only when its run, while ntpd does gradual but constant tweaking to keep
the system exactly where it needs to be, time-wise. Once it knows how your
computer runs, and has adjusted accordingly, it only uses occasional
external synchronization, to ensure nothing you've done has /changed/ the
way it syncronizes.
It's all in the ntp documentation, available to be read by anybody with an
interest in the subject or a need to know how it works.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
firstname.lastname@example.org mailing list