Atanas Vladimirov wrote on 09.10.2026 12:06:
On 2026-10-08 17:59, Thomas Kupper wrote:
Hi
A ping, with text and all :
End of August 26 chrony 4.9 was released with support for OpenBSD
including pledge(2) support and support for refclock driver for
OpenBSD timedelta sensors.
I'd very much welcome feedback and testing of chrony.
For anyone not knowing what chrony is used for, here a short
introduction:
chrony is a versatile implementation of the Network Time Protocol
(NTP). It can synchronise the system clock with NTP servers, reference
clocks (e.g. GPS receiver), and manual input using wristwatch and
keyboard. It can also operate as an NTPv4 (RFC 5905) server and peer
to provide a time service to other computers in the network.
The news about 4.9 (and previous versions) can be found at :
https://chrony-project.org/news.html
Find attached the OpenBSD ports archive for it.
It run under the user _chrony which would have to be added to the
user.list beforehand with user ID 906, the lowest unused ID as of
today/2026-10-08.
---
diff -us infrastructure/db/user.list{.orig,}
--- infrastructure/db/user.list.orig Sun Aug 30 07:49:54 2026
+++ infrastructure/db/user.list Sun Aug 30 07:49:15 2026
@@ -414,3 +414,4 @@
903 _iaxmodem _iaxmodem telephony/iaxmodem
904 _neighbot _neighbot net/neighbot
905 _pgweb _pgweb www/pgweb
+906 _chrony _chrony net/chrony
---
/Thomas
Hey Thomas,
It's me again :)
I just wanted the thanks you again and to repeat myself that I'm running
this port since I fond it, and I'm very happy with it.
Here you can see how accurate my stratum 1 server running Chrony and the
refclock timedelta sensors is:
https://www.ntppool.org/a/don.nasco
I hope that we will have it officially in ports as soon as possible!
Thank you Atanas, kind of you to support the effort. I won't put Stuart
on CC since it seemed he got annoyed by your last email and let us know
that he has little motivation to test chrony. Maybe someone else will
take it on. I don't won't to upset anyone, especially not someone that
works so hard for OpenBSD.
The biggest pain - if not in ports - is changing the user id when
eventually another user with ID 906 will be created for a port that
makes it into port. That of course can be solved with a few lines of a
shell script.
But maybe it's easier if I change the user to _ntp in anticipation of
the port not getting in, what do you think?
/Thomas
Best wishes,
Atanas
