From: Thomas Kupper Subject: Re: [NEW] net/chrony -> Fwd: Chrony 4.8 for ports To: ports@openbsd.org Date: Tue, 3 Feb 2026 14:06:40 +0000 On 03.02.2026 13:48, Stuart Henderson wrote: > i'd be happier about having this in ports if the diffs supporting > openbsd were upstream, rather than coming from a fork. Sure, that makes sense. I'll see if I can get into upstream. /Thomas > > On 2026/01/24 17:00, Thomas Kupper wrote: >> Ping :) >> >> /Thomas >> >> >> -------- Forwarded Message -------- >> Subject: Chrony 4.8 for ports >> Date: Sat, 17 Jan 2026 11:53:28 +0000 >> From: Mailing Lists >> To: ports@openbsd.org >> >> Hi, >> >> Based on Shaun Ren's GH OpenBSD code (https://github.com/shaunren/chrony) I >> have created a ports package/git for Chrony 4.8. >> >> There are a few questions that came up. >> >> Regarding Chrony's source code: >> >> First off, the author - Shaun Ren - is for me just a name on a Github >> profile, no email or anything else. On www.mail-archive.com there is a Shaun >> Ren with entries from almost ten years ago on the linux-kernel mailing list >> with a @linux.com address. I opened an issue on GH 10 days ago informing >> him/her that I did create the port and asked a) if it is ok and b) if yes, >> if Shaun would add the copyright to all the files that where modified. >> >> What are the rules regarding the copyright of code and contact data needed >> from a code owner? Shaun added a copyright to the file sys_openbsd.c dating >> back to 2021 but not to now other file modified. >> >> Generally: Is there an interest to have Chrony in OpenBSD ports (if the >> copyright situation can be cleared)? Second if yes, would someone be willing >> to review Shaun's code? I'm not a skilled programmer and for me it looks and >> behaves ok. Certainly on the server it runs good, the numbers look find (for >> a VM in the cloud), NTS as a client and as a server works as expected. Shaun >> uses adjfreq(2) to adjust the clock and implemented privilege drop. >> >> It would be interesting to see it tested in very high load or with handling >> of lots request, how it behaves. >> >> Regarding the port itself: >> >> Chrony runs under its own user, _chrony. For now I manually added it to >> infrastructure/db/user.list. Alternative the already existing user _ntp >> could be used. Is there a preference to one or the other? The _chrony user >> id is 902. >> >> I could be the maintainer of the package but if bigger Chrony code changes >> are necessary, help would be needed. >> >> If anyone is interested, the port files are attached and the git repo can be >> found at sourcehut: >> >> https://git.sr.ht/~patient0/chrony-OpenBSD-ports, branch 'openbsd' >> >> For anyone still interested: >> >> There is another branch called 'flavor/nts-pool' that patches Chrony 4.8 to >> take part in the experimental NTP NTS pool of Trifecta Tech Foundation >> (ntpd-rs creator, https://trifectatech.org, I have no affiliation). At the >> moment I run two OpenBSD virtual servers (and a patched NetBSD) which take >> part in that project. >> >> >> /Thomas > >