3 ms·
openntpd has been nothing but trouble for me, but when I switched to djb clockspeed instead, it made things better. Here's a script that runs on GFiber devices
by apenwarr 12y ago
openntpd has been nothing but trouble for me, but when I switched to djb clockspeed instead, it made things better. Here's a script that runs on GFiber devices, which uses tlsdate securely for the initial timewarp, and djb clockspeed thereafter. Since switching to this we have had extremely accurate timekeeping.
https://gfiber.googlesource.com/buildroot/+/master/fs/skeleton/bin/run-tlsdate https://gfiber.googlesource.com/buildroot/+/master/fs/skelet...
- stock_toaster 12y agoWhich version were you using? If you were using the portable version, I heard openntpd-portable wasn't updated for quite a while, and fell behind...missing out on some really big improvements from more recent versions. The portable tree has apparently recently been picked up again by a new maintainer.
- busterb 12y agoIf you don't mind elaborating a bit more on the troubles you had, I might be able to help get things fixed for a later release. I have had some trouble on Solaris getting the adjtime olddelta value to settle quickly, but haven't heard of any other issues. Even if you're happy with clockspeed, it might help other users to identify the problem.