-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Pierre Jarillon wrote: | No! Even for a single computer ntpd is the _*best*_ solution.
Not every time. Especially if you are on dial-up or another intermittent link, where it does not make much sense to run ntpd non-stop, unless you have some external time source, e.g. a GPS receiver or a radio clock.
There is something called "burst mode" in ntpd 4.x and up, which solves this problem, but again it would have to be either a cronjob or something run from the ifup scripts (ntpd -q + iburst set).
| Ntpdate is useful only when you buy your PC or when you change the battery | which is on the motherboard.
Actually ntpdate is being retired according to ntp.org (didn't know that either). The idea for ntpdate is to set the initial time, when the clock is way off and it would take ages for ntpd to synchronize it by slowing down or speeding it up. And that is not only in case of a new machine - I am not talking about servers with long uptimes here - many people turn their machines off when they are done for the day.
| Please, read carefully http://ntp.org or | file:/usr/share/doc/ntp-4.1.1/index.htm
Did so, there is nothing saying that running ntpd non-stop is the best thing after sliced bread.
Jan
- --
Jan Ciger VRlab EPFL Switzerland GPG public key : http://www.keyserver.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/mdOEn11XseNj94gRAqidAJwPhwYVNjhLbVqwHOQaaIzBoL6TywCg2hAR OsBpdTH6++4lOAPGLmbW50M= =3vxm -----END PGP SIGNATURE-----