| 1 |
Hemmann, Volker Armin posted |
| 2 |
<200602112357.00015.volker.armin.hemmann@××××××××××××.de>, excerpted |
| 3 |
below, on Sat, 11 Feb 2006 23:56:59 +0100: |
| 4 |
|
| 5 |
> today ntpd is the server daemon, for syncronizing several machines of a |
| 6 |
> network, ntp-client the part, that sets your clock. |
| 7 |
> please run ntp-client and forget ntpd. |
| 8 |
|
| 9 |
That's not exactly correct. Correct that ntpd is a server that /can/ |
| 10 |
serve to sync a number of machines, but in so doing, it keeps /far/ better |
| 11 |
time than simply stepping the clock with ntp-client will do. ntp-client |
| 12 |
is a single-shot deal that syncs your time with whatever server you are |
| 13 |
syncing to every time you run it -- that's it. ntpd will, once it knows |
| 14 |
how your computer behaves time-wise, be able to keep your computer much |
| 15 |
more accurate than it'd be on its own, even without a net connection or |
| 16 |
external time source to syncronize with -- and much more accurately than |
| 17 |
ntp-client can do as well, because ntp-client is doing jerky adjustments |
| 18 |
only when its run, while ntpd does gradual but constant tweaking to keep |
| 19 |
the system exactly where it needs to be, time-wise. Once it knows how your |
| 20 |
computer runs, and has adjusted accordingly, it only uses occasional |
| 21 |
external synchronization, to ensure nothing you've done has /changed/ the |
| 22 |
way it syncronizes. |
| 23 |
|
| 24 |
It's all in the ntp documentation, available to be read by anybody with an |
| 25 |
interest in the subject or a need to know how it works. |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman in |
| 31 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
Archives