1. Is this reproducible? Since the bug was created so long ago, I don't recall any more detail than above. Sorry...
Running in VMware Server 1.x VMs under some conditions makes time in the VM run really oddly. Perhaps the above hit a race condition where: 1) ntpd polled and time was OK 2) ntptrace ran live and realized time was out of sync 3) But since ntpd was between polling cycles it didn't realize that yet, so we see a disconnect in what ntptrace says vs. what ntpd had logged? 4) Then at 2009-03-30_17:57:48 ntpd resynced? I dunno, that's all a wild guess. This remix from the above session, times in EDT, might make both the problem and my wild guess a little more clear: 2009-03-30_17:49:19: ntpd: time reset -2.120918 s 2009-03-30_17:52:22: ntptrace: localhost: stratum 16, offset 0.000000, synch distance 0.013815 2009-03-30_17:57:48: ntpd: synchronized to 192.168.1.11, stratum 2 -- ntptrace reports wrong results https://bugs.launchpad.net/bugs/351980 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
