Worried about time? BSDCan early registration ends April 30th! Worried about network time? Henning Brauer is giving the talk: OpenNTPD - 20 years and a few milliseconds later at BSDCan 2026:

OpenNTPD hit the OpenBSD CVS in late 2004. Now, 20 years and a few milliseconds later, it's time to look back, how it was received, and what changed.

We'll briefly look at the world 20 years wrt having systems' clocks synchronized (or not), the design of OpenNTPD and how it fundamentally differed from everything around back then, and how it was - intentionally or not - misunderstood by some with very little knowledge but a lot of opinion, and how FUD from 20 years ago is still around. We'll cover what changed in OpenNTPD after it went public, and what changed in OpenBSD to increase accuracy substantially. We'll also cover the later added constraint feature to further defend against getting fed incorrect time.

#OpenNTPD #bsdcan #openbsd #cvs #time

Needed an #NTP server on a Raspberry Pi. To keep it light, I chose #OpenNTPD.

Not a great idea.

If your clock is off by more than 180 seconds, it won't adjust it; logs say

adjtime failed: Invalid argument

Now, according to the man page, it will jump to adjust larger offsets on startup, but apparently #Debian has patched this to require adding `-s` to /etc/default/openntpd.

They also don't support `constraint from` config stanzas used to get a trusted date via HTTPS.

Trying #chrony now.

Anyone else getting these warnings when running #OpenNTPD on either #FreeBSD or #HardenedBSD ?

I don't really know what that failure is or what it means. I don't know if I should take action--or even what kind of action to take.

with my #MIDI to WiFi "port" I seem to have accidentally fixed a bug in #OpenNTPd
tbh likely only in the linux port, not in the #OpenBSD original.

meanwhile it's #fantasound (stereo+1=3)

https://github.com/openntpd-portable/openntpd-portable/issues/76