Closed teto closed 6 years ago
As shipped, the check for NTP is hard-wired into the code and isn't configurable. Making it configurable with a command-line switch wouldn't be difficult.
The obvious hack (and you'd be on your own with this) is to build a version of owampd without the check. The danger is that if time sync is lost and the clock starts to drift, OWAMP will come up with wrong answers and the client will be none the wiser. I'd have to go check the RFC for the OWAMP protocol to see if there's anything that lets the server signal the client that its clock isn't in sync.
I thought this was fatal to the server as it died afterwards without any other message. After an strace, I managed to get a working systemd service and packaged the program for nixos https://github.com/NixOS/nixpkgs/pull/41485 .
Thanks for the great soft.
Hi Mark, this is still an issue on 5.0.7. I guess for supporting chronyd and eventually ptpd, there will need to be a fix? I currently can't get a demo to work using the docker testpoint. I made sure the host system has ntpd running and I still get: owping returned an error: owping: ntp_adjtime(): Operation not permitted;owping: NTP: STA_NANO should be set. Make sure ntpd is running, and your NTP configuration is good.;owping: ntp_adjtime(): Thanks, Shawn
@ShawnMcKee At some point, we're going to have to reckon with getting this implementation of OWAMP untied from NTP and smart enough to figure out sync on systems using other methods. Probably sooner rather than later since perfSONAR is moving away from distributions that run NTP.
Trying to package owamp for my distrib as I need to use it. It seems that it only supports ntpd since on start I have:
I got openntpd running
is there any configure flag/hack I could use to bypass this check ? I guess it shouldn't be too hard to replace openntpd with legacy ntpd but if I could work around it that would be cool.
Thanks for the great tool.