nanog mailing list archives
Re: Cost effective time servers
From: Jay Hennigan <jay () west net>
Date: Mon, 24 Jun 2019 19:18:22 -0700
On 6/21/19 07:57, Quan Zhou wrote:
Yep, went through the same route until I figured out that GPS time is a bit ahead of UTC.
The data from GPS includes the offset value from UTC for leap-second correction. This should be easily included in your time calculation. It's presently 18 seconds.
-- Jay Hennigan - jay () west net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV
Current thread:
- Re: Cost effective time servers, (continued)
- Re: Cost effective time servers Mel Beckman (Jun 21)
- Re: Cost effective time servers Warren Kumari (Jun 21)
- Re: Cost effective time servers Jay Hennigan (Jun 21)
- Re: Cost effective time servers Niels Bakker (Jun 21)
- Re: Cost effective time servers Denys Fedoryshchenko (Jun 21)
- Re: Cost effective time servers Tony Finch (Jun 21)
- Re: Cost effective time servers Tom Beecher (Jun 21)
- Re: Cost effective time servers Niels Bakker (Jun 21)
- Re: Cost effective time servers Andy Ringsmuth (Jun 21)
- Re: Cost effective time servers Quan Zhou (Jun 24)
- Re: Cost effective time servers Joe Abley (Jun 24)
- Re: Cost effective time servers Jay Hennigan (Jun 24)
- Re: Cost effective time servers Chris Adams (Jun 24)
- Re: Cost effective time servers Forrest Christian (List Account) (Jun 24)
- Re: Cost effective time servers Chris Adams (Jun 24)
- Re: Cost effective time servers Forrest Christian (List Account) (Jun 24)
- Re: Cost effective time servers Eric S. Raymond (Jun 24)