On Tue, 08 Sep 2009 14:06:28 +0200, Ray Burkholder
One unorthodox solution would be to run NTP (www.ntp.org) on your servers. This will keep the time in sync. There should be no need for changing time on the system.
I guess that some of my customers will indeed run NTP, or some other automatic adjustment. But only occasionally when the system is connected during service. Even then, I think that it wound get a very accurate clock source. The service tool is probably a laptop, not connected to anything else during the service. Then when NTP adjust the clock we have the problem. But it's not just me. asio is a library for everyone it should behave better. I still hope to learn how to make it do that. (Although it should be default). After all, windows have timers like GetTickCount and QuaryPerformanceCounter, on Linux I think times() could be used to get a continuous nonjumping clock. A clock like that is what we need to make small timeouts for communication purposes. -Bjarne