On Sun, Apr 15, 2001 at 12:06:01PM -0400, Mark Hurley wrote:
> Correct me if I'm wrong. ntp allows receiving (setting host computer
> time/date) and broadcasting (a lot of options) of date/time to
> internal (or external) lan.
>
> ntpdate ONLY acts as a client. Setting the (host) with the correct
> date/time.
That is correct. ntpdate is a single-shot client, it fetches the time (or
calculates an average from a few tries) and sets the time. Nothing fancy.
Once the time is approximately correct[1], ntpd is run and it periodically
checks the upstream ntp servers for the correct time and adjusts the local
clock accordingly.
And the same ntpd can be used as a local 'proxy' for other clients to
synchronize against. You can even run ntpd in peer-to-peer fashion, just
to keep the clocks relatively correct.[2]
[1] ntpd refuses to start if the time difference between local clock and
ntp server(s) is too large
[2] Ok, I cheated too, I haven't run ntpd in peer-to-peer mode, but the
docs said so... :)
--
Tommi Komulainen Tommi.Komulainen@iki.fi
GPG 1024D/68388EE6 6FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6
Attachment:
pgpBQ7rQgvNAq.pgp
Description: PGP signature