This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second

Previous message (by thread): [mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second
Next message (by thread): [mat-wg] New on RIPE Labs: Using RIPE Atlas to Validate International Routing Detours

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Stephen Strowes sds at ripe.net
Tue Jan 17 10:45:42 CET 2017

> On 16 Jan 2017, at 19:23, Gert Doering <gert at space.net> wrote:
> 
> On Mon, Jan 16, 2017 at 10:11:22AM +0100, Mirjam Kuehne wrote:
>> https://labs.ripe.net/Members/stephen_strowes/reviewing-the-2016-leap-second
> 
> I find the statement
> 
> "While many of our RIPE Atlas anchors are configured to skew time back towards UTC when a change is detected (as above), some of the older anchors are configured to observe the leap indicator in NTP responses and respond to it by stepping system clocks backwards"
> 
> quite interesting.  
> 
> Do not all anchors run the same software?  If not, why not?


The NTP daemons on the v1 and the v2 anchors are configured differently. The difference wasn’t intentional, but it did provide us with an interesting comparison!

S.

Previous message (by thread): [mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second
Next message (by thread): [mat-wg] New on RIPE Labs: Using RIPE Atlas to Validate International Routing Detours

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ mat-wg Archives ]