* Clint Pachl  [2007-10-24 00:45]:

quoted text
> Henning Brauer wrote:

>> * Boris Goldberg  [2007-10-23 15:50]:

>>

>>> CP> One  system  would  get time from the NTP pool and all other servers

>>> on

>>> CP> the network would sync to the local server.

>>>   You  don't  really  need ntpd on all systems. One (timeserver) runs

>>> ntpd,

>>> and others use rdate, called from cron (once a day is usually enough).

>>>

>>

>> that is bad advice.

>> it is not only much more work to set up, it also doesn't remotely yield

>> the same results. ntpd is much much better, since it doesn't rely on a

>> single answer from soem server to set the clock, and because it adjusts

>> the clock frequency over time.

>> there is not much point in using rdate at all.

>>

>

> From what I have read in this thread, it looks like only one guy prefers

> the old timed and rdate tools. A few are even telling him he is giving bad

> advice when promoting the usage of these tools. Henning mentioned that

> rdate and timed are pretty much useless and others have said that timed is

> obsolete. So why don't we remove them from the source tree?

rdate has an ntp mode, that is useful for checking/monitoring/debugging

ntp servers, so it'll stay.
timed might indeed be a candidate for the Attic.
--

Henning Brauer, hb@bsws.de, henning@openbsd.org

BS Web Services, http://bsws.de

Full-Service ISP - Secure Hosting, Mail and DNS Services

Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam