| Re: [chrony-dev] [PATCH] refclock: add SENSORS driver for OpenBSD timedelta sensors |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Subject: Re: [chrony-dev] [PATCH] refclock: add SENSORS driver for OpenBSD timedelta sensors
- From: Atanas Vladimirov <vlado@xxxxxxxxx>
- Date: Thu, 16 Jul 2026 19:27:59 +0300
- Cc: chrony-dev@xxxxxxxxxxxxxxxxxxxx, tom@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdbg.net; s=dkim; t=1784219279; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b/zBdHN7cxxMXRtz6zuigpRuo8bwY4fuBs/+xk9Khvo=; b=OJ/+g/hHolMzVDqj2EDHKq0KtZG9f2vn38pzkogA49Mm5xGLvNMSZwKw7dgMmDZoWrS+yQ hQ/iSPryathiLvh9Fvz1uA+DHJkwcmKK/BR+5N5mT45lu4M6nFs4Q7FOCV9YJ246LuBOcu OLhYFXEE7npEgBCRepCRW+LFOSNjvPu6+cVU2VS8nQnRHq9P1HZdePNdKnTAN/VVfJ8Kkd ucmwJMfIXY9v4WtgHFhx9iGXWXtVtGZ6DGVisCD1u0Nr50unUh6Fplblbya0tgK2N+8pYu Y9oFQLAbS2e/JPU+WI2iVev7D5+UkOMo/qBDD45GK3IVaolMYkvXlwb9iHUL+A==
On 2026-07-16 17:43, Miroslav Lichvar wrote:
> On Tue, Jul 14, 2026 at 12:12:45AM +0300, Atanas Vladimirov wrote:
>> This patch adds a new refclock driver for OpenBSD, which reads timedelta sensors from the hw.sensors sysctl framework.
>
>> Until now (last few months since I test it) the only way to use these sensors with chronyd was an external bridge program feeding the SOCK refclock.
>> A native driver removes that extra daemon and process boundary.
>
> Was that a big problem using that bridge? The code looks good (few
> comments below), but I hesitate to add and maintain a driver that
> will be probably used only by a very small number of users, and that
> I cannot even test. I have OpenBSD only as a VM. If it was accepted,
> would you stay around and keep an eye on it?
Hi,
Thanks for your reply and taking the time to review the patch.
I would say that even the bridge was working quite well,
it is not something that is good for production :)
I really would love to see this change merged upstream. It will make
live of other users easier, even I'm not sure how many of them will
run a Stratum 1 NTP server :).
To answer your other question - yes, I'll be here and will do all my best
to support that driver. It will be of my interest doing so.
I run an NTP server (ntp.bsdbg.net) since 2010 (you can check the history revisions
here https://support.ntp.org/Servers/PublicTimeServer000649?rev=8)
Now, I send an updated patch with your comments resolved and rebased on the latest master changes.
Let me know if anything else should be changed/updated.