User is no longer able to reproduce this.
Regards
chuck
** Changed in: ntp (Ubuntu)
Status: Confirmed = Invalid
--
ntptrace reports wrong results
https://bugs.launchpad.net/bugs/351980
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: ntp (Ubuntu)
Status: Incomplete = Confirmed
--
ntptrace reports wrong results
https://bugs.launchpad.net/bugs/351980
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
--
Ubuntu-server-bugs mailing list
Maybe this is a problem with vmware but vmware always had problems with
clocks.
Regards
chuck
--
ntptrace reports wrong results
https://bugs.launchpad.net/bugs/351980
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
--
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
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)
