>>| Never call a ntp server with cron! This is the best way to overload a >> ntp | server if several people do that. >>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 > > Change your thinking to a large scale sysadmin. Set up an NTP service > on one of your boxen and then configure all of your clients to sync in > whatever way you want to your local master. > >>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 > > No need. Again, set up your own NTP server, make all the local machines > sync to that one local master.
Of course, some solution for them to find the NTP server automatically (DHCP/DNS) would be nice (like _ldap._tcp kerberos-style SRV records do for nss_ldap/pam_ldap etc). Regards, Buchan
