NTP versus Systemd-timesyncd on the VOXL2
-
Hello,
Just a general question about timesyncd and how it is used in voxl-services. I installed NTP onto the VOXL2 without an issue and noticed that systemd-timesyncd can not run at the same time. So since systemd-timesyncd is just a simplified version of NTP that only perform as a client so there shouldn't be any issue. I have to double check with voxl-mavlink-server and the updating time stamps when not connected to the internet. That is really the only thing that I would foresee causing an issue. Not sure if anyone else would have an idea of anything else I should check?
Thank you for your time,
Aaron Porter -
Hello,
Just a general question about timesyncd and how it is used in voxl-services. I installed NTP onto the VOXL2 without an issue and noticed that systemd-timesyncd can not run at the same time. So since systemd-timesyncd is just a simplified version of NTP that only perform as a client so there shouldn't be any issue. I have to double check with voxl-mavlink-server and the updating time stamps when not connected to the internet. That is really the only thing that I would foresee causing an issue. Not sure if anyone else would have an idea of anything else I should check?
Thank you for your time,
Aaron Porter@Aaron-Porter , I believe the time sync services are interchangeable, such as
systemd-timesyncd,ntpd,chronyd. I don't think we have tried using anything other than the defaultsystemd-timesyncdon voxl2.If you try those out, please let us know if you find any issues! Thanks
Alex
-
@Aaron-Porter , I believe the time sync services are interchangeable, such as
systemd-timesyncd,ntpd,chronyd. I don't think we have tried using anything other than the defaultsystemd-timesyncdon voxl2.If you try those out, please let us know if you find any issues! Thanks
Alex
@Alex-Kushleyev we are seeing this issue with NTP were the time is saying that the Service has been running for 2 years 7 months when the VOXL2 is booted up. It doesn't seem to correct after that. I am looking into away to solve this issue but odd that TimeSyncd didn't have the same issue.
-
@Alex-Kushleyev we are seeing this issue with NTP were the time is saying that the Service has been running for 2 years 7 months when the VOXL2 is booted up. It doesn't seem to correct after that. I am looking into away to solve this issue but odd that TimeSyncd didn't have the same issue.
@Aaron-Porter , perhaps
systemd-timesyncdworks together withsystemdto correctly interpret the clock adjustments, so that run-time ofsystemdservices is properly calculated.Alex
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login