From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: comp.lang.ada Subject: Re: how to analyze clock drift Date: Fri, 21 Nov 2014 22:15:15 +0100 Organization: Aioe.org NNTP Server Message-ID: <87egswi7bw.fsf@debian.uxu> References: <6uun6alsp3jh1pob6g9qgcg85etqgenmd0@4ax.com> <87zjbn3nss.fsf@debian.uxu> <1nvfhit2csxr5.41v36jksch28$.dlg@40tude.net> <87k32qet5y.fsf@debian.uxu> <188uppnlnvqgq$.1kjz3jnhjxqji.dlg@40tude.net> <87fvdd38qi.fsf@debian.uxu> <87a93l35dm.fsf@debian.uxu> <9t7t6al8bmifd9krh6koiegttgsvcovadg@4ax.com> <87d28h1cj9.fsf@debian.uxu> <3apu6ap126abi6oalch9vpre20hjij2uon@4ax.com> NNTP-Posting-Host: feB02bRejf23rfBm51Mt7Q.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Notice: Filtered by postfilter v. 0.8.2 Cancel-Lock: sha1:R70ypiW3aad1PMFn4H2tjwa0Kls= Mail-Copies-To: never Xref: news.eternal-september.org comp.lang.ada:23616 Date: 2014-11-21T22:15:15+01:00 List-Id: Dennis Lee Bieber writes: > To measure actual clock variation you MUST have an > independent time-base for comparison. I'm starting to think this is a good idea. I thought the problem was sleep_until specifically, not all the C++ stuff, in what case using that to diagnose itself of course can't be done. So then, where do I get a better clock? My Linux gets it time from this command, I think (it was a while since a mucked around that stuff) ntpdate pool.ntp.org Is that considered reliable to the point it makes sense diagnosing sleep_until with that instead of the C++'s now()? -- underground experts united