Rhesa Rozendaal wrote:
Simple. Most system clocks aren't terribly accurate. It's quite easy to imagine one that runs slightly too fast. Now run e.g. "ntpdate pool.ntp.org" every so often, and see the clock go back :)

Rhesa (who runs ntpd on all his machines)

Tolkin, Steve wrote:
This would certainly violate the law of least astonishment! Please tell us more about this bug, where the system's clock sometimes can go backwards!


FYI: Take a look at the Time::HiRes XS code for Win32 platforms;
you'll be either chagrined or humored by the amount of code
required to get an accurate subsecond timer.

- Dean

Reply via email to