[EMAIL PROTECTED] wrote:
That server is clearly very broken. By the way, this is one of the reasons why you should NOT put an ntpdate command in a cronjob to sync your clocks. This is a very dangerous way to sync time, and you just found one of the dangers. Apparently you even do this on "a couple of servers". Even worse. Setup one or two real NTP servers in your company, using ntpd not ntpdate. This can be done on normal systems that are close to the Internet connection, no dedicated systems needed. Use 3 external systems to synchronize, not just one. Then, let your other servers use that to sync their clocks. Preferably also with ntpd. Windows systems can use SNTP (which is similar to ntpdate in a cronjob) but only to those internal servers that you trust. This will save you lots of mishap. Rob |
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
