4 ms·
I tried using OpenNTPd as the ntp client on a slow virtual server last year. It seemed like perfectly decent software except for the fact that it failed to kee
by mjw1007 10y ago
I tried using OpenNTPd as the ntp client on a slow virtual server last year.
It seemed like perfectly decent software except for the fact that it failed to keep the time in sync.
I switched to the usual (ntp.org) ntpd, with the same pool servers, and it worked fine.
- iso-8859-1 10y agoDid you try to diagnose the problem or did you just switch? I can't take such a vague bug report seriously.
- mjw1007 10y agoI didn't try to diagnose the problem. I just switched. I do not claim that OpenNTPD has a bug. Maybe it has requirements on the quality of the local clock that the virtual machine didn't meet. Maybe it has requirements on the remote time sources or the network that the setup didn't meet. What I do know is that over the years I've deployed ntp-over-the-Internet in a dozen or two different setups (including some user-mode-Linux ones with really poor local clocks), and ntp.org's ntpd has always managed to sync the clock. The one time I gave OpenNTPD a go it didn't. Looking at the log, I was running it for several months. After a while I got tired of fixing it manually when the clock was a few seconds out.