DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35746>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35746 ------- Additional Comments From [EMAIL PROTECTED] 2006-10-01 07:56 ------- (In reply to comment #5) > But the following statement demonstrates your limited knowledge of what NTP > goals are. > > An NTP client does not reset the clock when it computes a variation. It makes > the system clock tick faster or slower to narrow that variation over time. If > its too far out NTP will not function and abort. Since you know so much about how all implementations of NTP operate, perhaps you can explain to me how a datacenter I know of had all of their clocks jump forward by five minutes, then a couple hours later jump backwards by five minutes, and then repeat a couple more times over the next few days. This was under Windows, and was caused by a malfunction of their primary NTP server. Somehow, the primary NTP server jumping its clock caused all of the clients to jump their clocks, despite your knowledige of how NTP operates. The truth is that implementations of NTP can and do jump the clock, depending on how they are implemented and how large the time difference is. A well-mannered implementation of NTP operates exactly as you say. Not all implementations of NTP are well-mannered. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
