Open dschuermann opened 11 years ago
From chr...@fsfe.org on June 03, 2012 10:46:23 as for the interval, ntp-sync could keep track of the clock jitter and drift, and recommend an interval for fixing drift (without network sync) and an interval for fixingjitter (network sync) based on a given accuracy request.
From domschuermann@gmail.com on June 03, 2012 12:31:09 Puhh, that would really be a complicated implementation. I am sorry but I will not implement that due to my current time constraints. The current implementation now allows daily sync. I have changed the summary to reflect your new thoughts.
If anybody is interested in implementing this, please contribute!
From chr...@fsfe.org on June 03, 2012 23:22:21 fair enough; regular intervals will work reasonably and just lack the last ounce of efficiency.
if i some day decide to get started with android programming, this might be a good point to start.
From burcheri...@gmail.com on June 14, 2013 07:40:49 Hi. The implementation to set the time once per day is very important, thanks for that. Without using ntp-sync would not be an option for me as replacement for networks without NITZ data. As the first report already says I don't reboot often. The automatic drifting measuring I don't need, but a custom interval would be fine like interval in hours.
Original author: edoca...@gmail.com (May 21, 2012 09:19:14)
It would be useful if ntpsync could automatically sync date after a given interval of time (i.e. sync every 6 hours, every 12 hours, every 24 hours, every week, et cetera).
The "Set on boot" is fine, but I don't reboot my phone very often and my clock lags so I have to sync date manually.
Original issue: http://code.google.com/p/ntp-sync/issues/detail?id=5