In <[EMAIL PROTECTED]> Paul-Andrew Joseph Miseiko <[EMAIL PROTECTED]> writes:
> If the degree of change in your system clock is such that the list of > "potential" issues you listed below occured when running ntpdate every 12 > minutes you have bigger problems and "ntpd" will not provide any solution. It isn't just a really bad system clock that could cause the problems I described. It also depends on whether the clock slewing from the previous invocation of ntpdate has finished, how your OS deals with multiple adjtime() calls if it hasn't, whether your link to the internet was saturated during the time when ntpdate was called and a bunch of other things. The main point is still: doing an ntpdate ever 12 minutes generates over 5 times the load on the servers as using ntpd and will likely result in at least 5 times the error rate. Use ntpdate when you boot up your computer, or use it once per day if you don't care about your time. Otherwise use ntpd. -wayne _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
