Hi, I recently installed two OpenBSD systems from an i386 snapshot dated September 13th; one in a VMware machine and one on actual physical hardware.
A couple of days later I noticed that both servers were *not* date/time synced with the NTP server in my lab, even though I run OpenNTPD on all my OpenBSD servers. Afterwards I checked two other OpenBSD servers in the lab (also one running on VMware and another on physical hardware), one running an i386 snapshot from the end of March and the other one running a snapshot from the beginning of June. These two laters servers were both synced perfectly with the NTP server. I took a look at the /var/log/daemon file on all four servers and realized that the two unsynced servers do *not* have any "adjusting local clock by X.XXXXXXs" messages, while the two synced ones do. >From the logs it looks like OpenNTPD on the new servers *does* take note of the time delta beetn the server's local clock and the NTP server's time, yet it doesn't do anything to sync up the OpenBSD server to the NTP server. I installed a new VMware machine from an i386 snapshot I downloaded just a few hours ago dated September 24th to see if I'd have the same behavior as the September 13th servers; it turns out that I do, meaning that the server does not seem to sync via NTP either. I haven't noticed any other similar and recent comment about OpenNTPD problems on the list, so I'm fairly sure this is not a bug. Has anybody else observed the same behavior on their system? Has something changed recently regarding OpenNTPD that I've simply missed? Thanks, -Martin
