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