-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Pierre Jarillon wrote: | Le Vendredi 24 Octobre 2003 05:31, BOUTELIER Sébastien a écrit : |>My fourth wish is perhaps a detail but is it possible to have an option to |>synchronize the time with a NTP regularly in the "date and time" module of |>MCC ? (in fact use a ntp command with cron or at internet connection). | | | Never call a ntp server with cron! This is the best way to overload a ntp | server if several people do that. | Instead, use ntpd which is provided to call the server when needed and | does the best drift compensation for local clocks. The first aim of ntpd is | to make your time accurate, which is absolutely necessary to become a | server... if needed.
I think that the original idea was not to have non-stop synchronized clock (aka ntpd) but just the possibility to e.g. once a day synchronize clock with some external server. For desktop machines, this is usually enough, unless you have some special requirements.
To avoid the server overload (100+ machines syncing their clock at the same time), the script could be smart and randomize the time when it runs a bit. AutoRPM does this - when you pass it a special switch, it will wait for some random time (from few minutes up to several hours) and then do it's job. So it is OK to call this from the cron. I have such setup (with autoRPM to update 15 machines) and it works quite fine.
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/mT0wn11XseNj94gRAlzUAKC8JCmtBaNtTK/Xv6ocOEnr3q9kgQCfaTQA 8NjdjmFXevkWIynk3w6Xk1g= =LXYE -----END PGP SIGNATURE-----
